S01C5021 PDF

Users
Manual
Installation
IM 32S01C50-21E
IM 32S01C50-21E
3rd Edition

Introduction
This manual explains the procedure for installing the ProSafe-RS software and items to be set.
Be sure to read this manual before performing ProSafe-RS installation tasks.
Note that the Windows setup procedure (tasks corresponding to installation in this manual)
is not explained in this manual, as it is assumed that Windows has already been installed on
recommended PCs. If it is necessary to set up Windows, please refer to the Windows manual for
the procedure.
Note that process of copying of the ProSafe-RS software to the PC is referred to as installation
and the settings performed in Windows before/after the installation in order to run the ProSafe-
RS software on the PC are referred to as setup throughout this document, whereas in a normal
Windows context, the term installation tasks include the setup procedure.
This document is composed of the following chapters:
Chapter 1: How to Read this Manual

This chapter provides the overview of the installation tasks.
Chapter 2: Confirmation of Hardware Setup
This chapter describes the hardware settings that should be carried out before installing the
software.
Chapter 3: Windows and Network Setup on General-purpose PCs
This chapter explains Windows settings and network settings required for the ProSafe-RS
software to run.
Chapter 4: New Installation of ProSafe-RS Software
This chapter describes the first-time installation procedure of the ProSafe-RS software and
related precautions.
Chapter 5: Addition of ProSafe-RS Software Packages (without Revision Upgrade) and
Reinstallation
This chapter describes the procedure to add packages without upgrading the ProSafe-RS
software and reinstalling the software as well as related precautions.
Chapter 6: Revision Upgrade of ProSafe-RS Software
This chapter describes the procedure to upgrade the ProSafe-RS software revision and
related precautions.
Chapter 7: Troubleshooting
This chapter describes the causes and remedies for network-related problems and other
similar problems.
Chapter 8: Backup
This chapter describes how to backup the system regularly as a precaution against
unexpected troubles.
Chapter 9: Cautionary Notes for Upgrading ProSafe-RS
This chapter describes cautionary notes for the ProSafe-RS revision-ups.
Chapter 10: Installing the Common Functions of ProSafe-RS Software
This chapter describes how to install the Common Functions of ProSafe-RS Software to the
PC where no other ProSafe-RS package is installed when ProSafe-RS is integrated with
CENTUM.
Chapter 11: Security Setting Utility
This chapter describes how to use the Security Setting Utility to harden the SENG of
ProSafe-RS (by applying the improved Windows security features to enhance the system
security) and the security practices.
Chapter 12: Setting of Windows Domain Environment
This chapter describes the required settings when ProSafe-RS acts with Windows domain
environment.
Media No. IM 32S01C50-21 (CD) 3rd Edition : Dec. 2009 (YK) IM 32S01C50-21E 3rd Edition : Dec.22,2009-00
All Rights Reserved Copyright 2008, Yokogawa Electric Corporation
ii
ProSafe-RS Document Map

Safety System
Engineering
Safety Manual
Guide
IM 32S01S10-21E IM 32S01C10-21E
Software
Safety Control Station Integration with Open Interfaces

Reference CENTUM VP/CS 3000
IM 32S03B10-21E IM 32S01E10-21E IM 32S05B10-21E
Engineering Utilities and Messages

Reference Maintenance
Reference
IM 32S04B10-21E IM 32S04B20-21E IM 32S02B10-21E
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
IM 32S01C50-21E 2nd Edition : Dec.15,2008-00

iii
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.
Indicates that main switch is ON.
Indicates that main switch is OFF.
IM 32S01C50-21E 1st Edition : May 30,2008-00

iv
n Notes on Handling User Manuals

Please hand over user manuals to your end users so that they can have them on hand for
convenient reference.
Please read the user manuals thoroughly before using the product.
The purpose of these user manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
YOKOGAWA reserves the right to make improvements in the user manuals and product at
any time, without notice or obligation.
If you have any questions, or you find mistakes or omissions in the user manuals, please
contact our sales representative or your local distributor.
n Warning and Disclaimer

The product is provided on an as is basis. YOKOGAWA shall have neither liability nor
responsibility to any person or entity with respect to any direct or indirect loss or damage arising
from using the product or any defect of the product that YOKOGAWA can not predict in advance.
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:
l Commonly used Conventions throughout User manuals:
Character strings in the following font and style:

Indicate that user must enter them in the relevant field or text box in the context.
Example:
FIC100.SV=50.0
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).
S0001 TUN
Character string enclosed by brackets ({ }):

Indicates an option that can be omitted.
Example: Parameters for calling the tuning view on HIS
Tagname TUN {-Window size} {=Display position}
l Conventions used to show Key or Button Operations:
Characters enclosed by square brackets ([ ]):

Characters enclosed by square brackets within any description of a key or button operation,
indicate either a key on the keyboard, a button name on a window, or an item displayed on a
window.
Example:
Click the [OK] button.
l Conventions of User Defined Folder

User-Defined Folder Name
If the path of a folder can be defined by users, it is written within parentheses.
Example: (RS Project Folder) \SCS0101
If the RS Project Folder is C: \MYRSPJT, the above path becomes: C: \MYRSPJT\SCS0101

vi
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
Indicates a source to be referred to.

Clicking a reference displayed in green can call up its source, while clicking a reference
displayed in black cannot.
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.
n Integration with CENTUM

ProSafe-RS can be used by integrating with CENTUM VP or CENTUM CS 3000. In the Users
Manuals of ProSafe-RS, the integration with CENTUM VP or CENTUM CS 3000 is referred to as
Integration with CENTUM.
For the same features of CENTUM VP and CENTUM CS 3000 that have different feature names,
the name used in CENTUM VP will be referred to in the explanations. (For example, CENTUM
CS 3000 System Alarm Window and CENTUM VP System Alarm View have the same functions,
but only System Alarm View will be referred to when explaining this feature.) Nevertheless,
if there is any difference in functionality according to whether ProSafe-RS is integrated with
CENTUM VP or CENTUM CS 3000, the feature will be explained separately for both cases.
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).

vii
n About Explanation of System Behavior

In this manual, system behavior is explained assuming the use of the latest software and
hardware that Yokogawa provides at the publication of the manual. Wherever a topic needs
explanation of earlier revisions of software or hardware, a link to the required explanation is
provided so that you can read them according to your system.
n About Station Types

Safety control stations (SCS) are named as follows according to the CPU node (SSCx0S/
SSCx0D) and CPU module (SCP4x1) mounted in them.
SCSV1-S : SCS that uses SSC10S/SSC10D (SCP401 is installed)
SCSP1-S : SCS that uses SSC50S/SSC50D (SCP451 is installed)
SCSP2-S : SCS that uses SSC60S/SSC60D (SCP461 is installed)
To explain the functions of these different types of SCS, the following generic terms or
abbreviations may be used in this manual.
SCS : Generic term that denotes all types of SCS
SCSV : SCS connected on V net (this denotes SCSV1-S)
SCSP : SCS connected on Vnet/IP (this denotes SCSP1-S and SCSP2-S)
SCSV1 : Abbreviation for SCSV1-S
SCSP1 : Abbreviation for SCSP1-S
SCSP2 : Abbreviation for SCSP2-S
IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

viii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the DVD-ROM or CD-ROM shall
remain in Yokogawa.
You are allowed to print out the required pages of the online manuals for using the product,
however, you are not allowed to print out the entire document.
Except as stated above, no part of the online manual may be reproduced, either in electronic
or written form, registered, recorded, transferred, sold or distributed (in any manner including
without limitation, in the forms of paper documents, electronic media, films or transmission via the
network).
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.

Toc-1
ProSafe-RS
Installation
IM 32S01C50-21E 3rd Edition
CONTENTS
1. How to Read this Manual.......................................................................... 1-1
1.1 Overview on Software Installation................................................................... 1-3
1.2 Information Security.......................................................................................... 1-9
2. Confirmation of Hardware Setup............................................................. 2-1
2.1 Hardware Setup for SCS .................................................................................. 2-2
2.2 Hardware Setup for General-purpose PC....................................................... 2-6
2.2.1 Address Setting of Control Bus Interface Card................................... 2-7
2.2.2 Mounting a Control Bus Interface Card............................................ 2-10
3. Windows and Network Setup on General-purpose PC......................... 3-1
3.1 Windows Setup.................................................................................................. 3-4
3.1.1 Windows Setup (Windows Vista/Windows Server 2008)......................3-5
3.1.2 Windows Setup (Windows XP/Windows Server 2003).................... 3-10
3.2 New Installation of Control Bus Driver.......................................................... 3-16
3.2.1 New Installation of Control Bus Driver (Windows Vista/
Windows Server 2008)..................................................................... 3-18
3.2.2 New Installation of Control Bus Driver (Windows XP/
Windows Server 2003)..................................................................... 3-24
3.3 Windows Network Setup................................................................................. 3-29
3.3.1 Setting Network Connection (Windows Vista/
Windows Server 2008)..................................................................... 3-30
3.3.2 Setting Network Connection (Windows XP/
Windows Server 2003)..................................................................... 3-43
3.4 Installation and Setup of Vnet/IP.................................................................... 3-52
3.4.1 Setup and Check Hardware (for Vnet/IP)......................................... 3-55
3.4.2 Installation of Network Drivers.......................................................... 3-58
3.4.3 Installation of Open Communication Driver (Windows Vista/
Windows Server 2008)..................................................................... 3-60
3.4.4 Installation of Open Communication Driver (Windows XP/
Windows Server 2003)..................................................................... 3-64
3.4.5 Setting Vnet/IP Network Connection (Windows Vista/
Windows Server 2008)..................................................................... 3-67
3.4.6 Setting Vnet/IP Network Connection (Windows XP/
Windows Server 2003)..................................................................... 3-75
3.4.7 Reinstallation (for Vnet/IP)................................................................ 3-80

Toc-2
4. New Installation of ProSafe-RS Software............................................... 4-1
4.1 New Installation of Software............................................................................. 4-1
4.2 User Account and Folder Settings................................................................... 4-6
4.2.1 Create User Accounts on Workgroup Member PC............................ 4-6
4.2.2 When Choosing Standard Model of Information Security.................. 4-7
4.3 Settings after Software Installation................................................................ 4-12
4.4 Online Manual Setting..................................................................................... 4-22
5. Addition of ProSafe-RS Software Packages
(without Revision Upgrade) and Reinstallation..................................... 5-1
5.1 Addition of ProSafe-RS Software Packages
(without Revision Upgrade).............................................................................. 5-2
5.2 Reinstallation of the ProSafe-RS Software..................................................... 5-6
6. Revision Upgrade of ProSafe-RS Software............................................ 6-1
6.1 Procedure for Updating Control Bus Driver................................................... 6-3
6.2 Revision Upgrade of ProSafe-RS Software (without Package Addition).... 6-8
6.3 Revision Upgrade of ProSafe-RS Software (with Package Addition)........ 6-11
6.4 ProSafe-RS Software Version Upgrade......................................................... 6-14
6.5 Settings after Upgrading ProSafe-RS Software........................................... 6-15
7. Troubleshooting........................................................................................ 7-1
7.1 Troubleshooting Related to Control Bus Driver............................................. 7-2
7.2 Windows Related Troubleshooting................................................................. 7-8
7.3 ProSafe-RS Software Installation Troubleshooting....................................... 7-9
7.4 Troubleshooting Related to Vnet/IP Open Communication Driver............ 7-11
8. Backup........................................................................................................ 8-1
9. Compatibility between Revisions and Cautionary Notes for
Upgrading................................................................................................... 9-1
9.1 Upgrading to R1.01.30....................................................................................... 9-2
9.2 Upgrading to R1.01.40/R1.01.50....................................................................... 9-6
9.3 Upgrading to R1.02............................................................................................ 9-8
9.4 Upgrading to R1.03.......................................................................................... 9-11
9.5 Upgrading to R2.01.......................................................................................... 9-15
9.6 Upgrading to R2.02.......................................................................................... 9-17
9.6.1 Cautionary Notes for Upgrading....................................................... 9-18
9.6.2 Compatibility with Earlier Revisions.................................................. 9-21
9.7 Upgrading to R2.03.......................................................................................... 9-23
9.7.1 Cautionary Notes for Upgrading....................................................... 9-24
9.7.2 Compatibility with Earlier Revisions.................................................. 9-26
10. Installing the Common Functions of ProSafe-RS Software............... 10-1
10.1 Installing SCS Simulator................................................................................. 10-8
10.2 Installation for Integration with CENTUM SOE Viewer ............................... 10-9
11. Security Setting Utility............................................................................ 11-1
12. Setting of Windows Domain Environment........................................... 12-1

<1. How to Read this Manual> 1-1
1. How to Read this Manual

Different procedures and settings are used for the installation method according to the
circumstances.
This chapter provides the users with an overview of which chapter to read first under
various circumstances.
Installation tasks
Installation on a general-purpose PC
New installation: Chapters 3 and 4
Upgrading revision: Chapter 6 and 9
Adding packages (without revision upgrade): Chapter 5
Reinstallation: Chapter 5
Security Setting Utility: Chapter 11
Chapter that must be read Chapters to be read as necessary

Chapter 1 Hardware configuration: Chapter 2
Troubleshooting: Chapter 7
Backup: Chapter 8
Installation of the Common Functions of
ProSafe-RS Software: Chapter 10
Setting of Windows domain environment: Chapter 12
010001E.ai
Figure How to Read this Manual
IMPORTANT
Using the Security Setting Utility supported in ProSafe-RS R2.01, the system can be hardened
(by applying the improved Windows security features to enhance the system security). Using
the Security Setting Utility to setup the security policies may result in some differences on the
installation procedure. It is necessary to decide the security policy for the entire system before
installing the system.
SEE
ALSO For more information about system hardening, see the following:
2.1.2, Information Security of the Engineering Guide (IM 32S01C10-21E)
1.2, Information Security
Since ProSafe-RS R2.01, the Windows PC for system can be managed in Windows domain
environment. When Windows domain environment is used, the setups for the Windows domain
environment become necessary. For ProSafe-RS R2.01 system, it can choose either Windows
domain environment or workgroup environment like for ProSafe-RS R1.03 or before. This should
be decided before installing the system.
SEE
ALSO For more information about setups of domain environment, see the following:
12, Setting of Windows Domain Environment

<1. How to Read this Manual> 1-2
n Overall Flow of New Installation Tasks

The following flowchart explains the overall flow of the ProSafe-RS installation tasks in a
simplified manner.
Start
1. SCS hardware setup See 2, Confirmation of Hardware Setup
This task is not required if Windows has already

2. Windows installation
been installed on a recommended PC.
3. Windows Service This task is not required if Windows Service Pack

Pack installation has already been installed on a recommended PC.
4. Windows setup See 3.1, Windows Setup.
Apply ProSafe-RS Y
in Windows Domain
Environment ?
5. Setup Domain Environment See 12, Setting of Windows
N (on domain server) Domain Environment
6. Installing V net interface card

See 2.2.3, Mounting a Control Bus Interface Card
in the general-purpose PC
7. Network setup See 3.3, Windows Network Setup
Was Windows Y
installed from the CD-ROM
in the tasks above?
8. Windows Service Pack
reinstallation
N
9. ProSafe-RS software
See 4, New Installation of ProSafe-RS Software
installation
10. Setup Information Securities See 11, Security Setting Utility
11. Electronic document setting See 4.2, Online Manual Setting
12. Settings after ProSafe-RS

See 4.3, Settings after Software Installation
installation
Create User Accounts

Define Desktop Properties
: Maybe affected by system hardening plan.
End
010002E.ai
Figure Flow of Installation Tasks

<1.1 Overview on Software Installation> 1-3
1.1 Overview on Software Installation

In this section, the hardware and software environments will be explained.
n Hardware Operation Environment
l With Windows Vista Operating System

CPU
Intel Core 2 Duo Processor 2.13 GHz or higher; Xeon Dual-Core 2.0 GHz or higher
Main memory
2.0 GB or more
Hard disk capacity
20 GB or more free space (Minimum); 40 GB or more free space (Recommended)
Display
SXGA (1280x1024) or higher resolution, True color (must); For wide monitoring, WXGA+
(1440x900) or higher.
Graphics
DirectX 9 graphic processing unit or equivalent and support the following:
- WDDM (Windows Driver Display Model) driver
- Pixel Shader 2.0
- 2 Bits/Pixel
- 128 MB Graphic Memory
l With Windows XP or Windows Server 2003 Operating System

CPU
Pentium 4, 1.8 GHz or higher
Main memory
512 MB or more
1 GB or more if shared with ENG/HIS of CENTUM VP
Hard disk capacity
10 GB or more
Display
SXGA (1280x1024) or higher resolution, True color (must); For wide monitoring,
WXGA+(1440x900) or higher.
Graphics
The graphic features that support Windows XP/Windows Server 2003
Color: 65536 or higher; VRAM: 4MB or larger
1024 x 768 (minimum); 1280 x 1024 (recommended)

l With Windows Server 2008 Operating System
CPU
Intel Core 2 Duo Processor 2.13 GHz or higher; Xeon Dual-Core 2.0 GHz or higher
Main memory
2.0 GB or more
Hard disk capacity
20 GB or more free space (Minimum); 40 GB or more free space (Recommended)
Display
SXGA (1280x1024) or higher resolution, True color (must); For wide monitoring, WXGA+
(1440x900) or higher.
l Peripheral devices
A CD-ROM drive and 3.5 FD drive are required.
A PCI slot or a PCI Express slot needs to be reserved for control bus interface card.
Prepare an MO drive and/or DAT drive or secure sufficient hard disk space for backup in
order to back up engineering data, which encompasses a project database, and various
databases used during operation.

n Software Operation Environment

The software operation environment is shown below.
l OS
The compatibility with the service packs will be described in next paragraph.
Windows XP Professional
Windows Vista Business Edition
Windows Server 2003
Windows Server 2008
64 bit operating system is not supported.
Windows 2000 is not supported.
l Correspondence between Windows OS Versions and Service Packs

The table below explains correspondence between the Windows OS versions/service packs and
ProSafe-RS.
Table Correspondence between ProSafe-RS Software Release Numbers and Windows OS Versions
Windows
Server
Windows Server 2003 Standard Windows Vista
ProSafe-RS Windows XP Professional Edition Business Edition
2008
Release Standard
Number Edition
SP1 SP2 SP3 SP1 SP2 R2 R2 SP2 SP1 SP2 SP2
R1.01
R1.01.30/
R1.01.40/
R1.01.50
R1.02
R1.03
R2.01/R2.02
R2.03
: Compatible
Blank: Inconpatible
When installing ProSafe-RS, confirm that a Windows OS version appropriate for the ProSafe-RS
software release number and an appropriate Service Pack is installed on the general-purpose
PC.
IMPORTANT
If Windows is pre-installed on a PC, various Windows utilities in addition to the operating
system (OS) itself may also have been installed. These utilities are not only unnecessary for the
operations of SENG but may also affect the operations; it is thus recommended to reinstall the
OS.
PCs recommended by YOKOGAWA are pre-installed at shipment in conditions where only the
necessary applications are installed.

l About .NET Framework and MDAC
.NET Framework (Version 3.5 SP1)
ProSafe-RS supports version 3.5 SP1 or later.
.NET Framework is automatically installed when the ProSafe-RS software is installed.
However, .NET Framework(Version 3.5 SP1) will not be automatically installed if a version
of .NET Framework newer than the one in the ProSafe-RS software CD-ROM is already
installed in the PC so as to avoid downgrade of .NET Framework.
MDAC (Version 2.7)
ProSafe-RS supports version 2.7 or later.
MDAC is automatically installed when the ProSafe-RS software is installed.
However, MDAC (Version 2.7) will not be automatically installed if a version of MDAC newer
than the one in the ProSafe-RS software CD-ROM is already installed in the PC so as to
avoid downgrade of MDAC.
MSXML (Version 4.0) Service Pack 2
ProSafe-RS supports version 4.0 Service Pack 2 or later.
MSXML is automatically installed when the ProSafe-RS software is installed.
However, MSXML (Version 4.0) Service Pack 2 will not be automatically installed if a version
of MSXML newer than the one in the ProSafe-RS software CD-ROM is already installed in
the PC so as to avoid downgrade of MSXML.
l About Coexistence with Other Software

The ProSafe -RS software can coexist with the following software.
The table below lists software that has been confirmed to function without problems together with
ProSafe-RS.
Table List of Software that can Coexist with ProSafe-RS
Classification Software name Version (*1) Remarks
2003 (XP) + SP1, SP2 or SP3
Spread sheet Microsoft Excel (*2)
2007 + SP1
2003 (XP) + SP1, SP2 or SP3
Word processor Microsoft Word (*2)
2007 + SP1
Microsoft Visual C++ 2008
Software development
Microsoft Visual Basic 2008
Adobe Acrobat 7.0.0 (*3), 8.1.0 (*3), 9.2 Used for the electronic
Document viewer
Adobe Reader 7.0.9 (*3), 8.0.0 (*3), 9.2 document package
6.0+SP1 or SP2
WWW browser Microsoft Internet Explorer (*2)
7.0
Others APC PowerChute Business Edition 7.0.4, 7.0.5
*1: It is necessary to check the software requirements respectively for the required operating environments.
*2: SP is an abbreviation of Service Pack.
*3: Required only when integrated with CS 3000; otherwise, not required.
l Coexistence with PRM

The version of PRM should be R3.02.00 or later. Note that SCSP2 stations are only supported by
PRM R3.04 and later. If you integrate ProSafe-RS with FAST/TOOLS, the version of PRM should
be R3.03.00 or later.

l Coexistence with Exaopc
The version of Exaopc should be R3.60 or later. If the version of Exaopc older than R3.60 is
used, there are the following usage restrictions:
The system alarm messages added in ProSafe-RS R2.03.00 will not be displayed.
The process alarm messages output from the mapping blocks added in ProSafe-RS
R2.03.00 will not be displayed.
The correct operations cannot be guaranteed if the ProSafe-RS software coexists with other
kinds of software.
n About Coexistence with CENTUM System

Confirm the following points if the ProSafe-RS software is installed on a general-purpose PC that
is used as an ENG/HIS of a CENTUM system.
To make ProSafe-RS coexist with a CENTUM system, be sure to use the following
combination of system release numbers.
Table Correspondence between ProSafe-RS and CENTUM Release Numbers

ProSafe-RS CS 3000 CENTUM VP
R2.01/R2.02 R3.06 or later (*1) R4.01 or later
R2.03 R3.06 or later (*1)(*2) R4.02 or later(*2)
*1: When integrated with CS 3000, there will be the following restrictions:
When integrated with CS 3000, system can not be hardened.
When subsystem communication (Modbus) or SYS_SEC_CTL FB is applied, R3.07 or higher is required.
If a project has any of the following, CS 3000 R3.08 or later version is required:
- The manual operation function block (MOB_11, MOB_21, MOB_RS, MOA)
- The SCS with Vnet/IP network
If a project has any of the following, CENTUM CS 3000 R3.08.50 or later version is required.
- SCS Simulation Test
- Interface for Plant Training
- SCS Link Transmission
- Grouping override function block
- Enhanced Password FB
- Enhanced CS 3000 Integration Function in ANLG_S block
*2: When integrated with CS 3000 or CENTUM VP of the version earlier than R4.02, these are the restrictions:
Operation and monitoring of SCSP2 are not available.
Annunciator messages of ANN_FUP are not displayed.
The system alarm messages added in ProSafe-RS R2.03 are not displayed. When automatic IOM downloading takes place,
the same message as the one displayed when IOM downloading is manually executed is displayed.
The control bus driver in ProSafe-RS software CD-ROM should be used for installation,
unless otherwise specified.
If either of the systems is upgraded, follow the instructions for each revision.
SEE
ALSO For more information about revisions of each ProSafe-RS release, see ProSafe-RS Release Information
(IM 32S01A50-21E)
For more information about revisions of each CENTUM release, see the following:
CS 3000 Electronic Document Addendum (IM 33Q01A50-01E) and CS 3000 Installation (IM 33Q01C10-
01E)
CENTUM VP Electronic Document Addendum (IM 33M01A50-40E) and CENTUM VP Installation (IM
33M01A20-40E)
When ProSafe-RS software coexists with CENTUM software in the same PC, the setups
of Windows should follow the instructions in the Installation Manual of CENTUM. However,
the virtual memory size for the CS 3000 in Windows XP/Windows Server 2003 environment
should follow the instruction described in this document.

n Types of ProSafe-RS Software Installations

There are the following types of ProSafe-RS software installation. Select an installation type
appropriate for your purpose and perform the corresponding operations.
l New Installation
New installation refers to installing the ProSafe-RS software on a PC on which the software has
not been installed before. A keycode FD is required to complete the installation. Before finishing
the installation, the setups for system hardening need to be performed.
l Reinstallation
Reinstallation refers to installing the same ProSafe-RS software revision again on a PC on which
the ProSafe-RS software has already been installed. The keycode FD is not used. Use the CD-
ROM containing the same revision of the software as the one installed on the PC.
l Additional Installation
Additional installation refers to an installation where additional ProSafe-RS packages are
installed on a PC on which the ProSafe-RS software has already been installed. The keycode
FD containing the code for the package to be added is required. Use the CD-ROM containing the
same revision of the software as the one installed on the PC.
l Revision Upgrade (without Package Addition)

This refers to installation for the purpose of upgrading the revision of the ProSafe-RS software
already installed on a PC. The keycode FD is not used because no package will be added. Use a
CD-ROM containing a newer revision than the one installed on the PC.
l Revision Upgrade (with Package Addition)

This refers to installation for the purpose of upgrading the revision of the ProSafe-RS software
already installed on a PC. The keycode FD containing the code for the package to be added is
required. Use a CD-ROM containing a newer revision than the one installed on the PC.
l Version Upgrade
The version upgrade installation means to upgrade from a lower version to a higher version. For
example the version upgrade from R1.03 to R2.01, the version number next to R increases by 1
or more.
When running the version upgrade installation, the Keycode FD and CD-ROM of the new version
software are required.
TIP
The installer for the above described installation may behave differently in accordance with the following
circumstances:
Whether the hard disk contains the Keycodes.
Whether the Keycode FD is used or not at the installation.
Combinations between the installed version of ProSafe-RS in the PC and to be installed version of
ProSafe-RS CD-ROM.

<1.2 Information Security> 1-9
1.2 Information Security

When installing R2.01 or later version of ProSafe-RS software, the Security Setting
Utility will start after the new installation. The security type needs to be selected and the
selected type must match the application environment of ProSafe-RS. The PC hardening
settings can be defined at any time by manually starting the Security Setting Utility
provided in the ProSafe-RS software CD-ROM.
n PC Hardening Setting Models

PC hardening models are categorized as follows according to the strengthened level of the
security:
l Standard Model
The standard model is a system hardened model. The system hardening feature is supported
since ProSafe-RS R2.01. This security model is categorized into two types according to the PC
management on the Windows network.
Windows Domain Type
This is a model that uses the Windows domain controller features to manage the users in
Windows domains and user groups. Before setting the system hardening in the Windows
domain environment, the Windows Domain Controller needs to be installed.
SEE
ALSO For more information about setting the domain environment, see the following:
Stand alone Type

Same as in ProSafe-RS R1.03 and previous versions, a PC can belong to a Windows
workgroup and manages the users and user groups in each PC. In this type, the user
accounts can be managed in each PC, but it is necessary that all related PCs manage the
same relationship between the user accounts and the user groups.
l Legacy Model
By using the legacy model, the same security management levels for RS project files, the access
control of registry and the DCOM settings as in ProSafe-RS R1.03 and previous versions can be
set. This model should be selected if the system consistency is emphasized.
IMPORTANT
This model must be selected if a PC is connected with a CS 3000 system earlier than R3.08 or a
CENTUM VP system that is already applied with the legacy model.
TIP
In Windows environment, the PC hardening settings can be manually strengthened. The security model
established by this method is referred to as Strengthened Model.

n Items for Security Setting

If you select the Standard Model security type, you can strengthened the items below:
Table Security Setting items
Category Security Setting Description
Create User Group Creates user groups for access controls
Program Access Control Restricts each user group for running programs
Access Control Restricts each user group for accessing the files under
Folder Access Control
each folder
Registry Access Control Restricts each user group for accessing registries
DCOM Access Control Restricts each user group for accessing DCOM
DCOM Settings Dynamic Restriction on DCOM Restricts utilizing the DCOM ports according to a range
Ports of port numbers
Enables Windows firewall. Only the predefined
Firewall Settings Windows Firewall
destinations are allowed to connect with ProSafe-RS.

n User Groups for Standard Model

The privileges of the ProSafe-RS user groups for the Standard Model security type are as
follows. The legacy model of security settings is irrelevant to the user groups.
Some user groups are automatically created by Security Setting Utility while some other user
groups need to be created manually. The user groups in both cases are also listed in the table
below:
Table User Groups with Standard Model of Security Settings
Domain Workgroup
User group Name Description
Member PC Member PC
This is the group for CENTUM VP operators accessing the
PSF_OPERATOR Manual Auto
ProSafe-RS on integration with CENTUM VP.
PSF_ENGINEER User group for ProSafe-RS engineers. Manual Auto
PSF_OPC User group for OPC communication users. Manual Auto
This group has the same privilege as PSF_OPC. The user
that cannot work in the domain environment such as the
PSF_OPC_LCL built-in user of the EXA package can added to this local user Auto -
group. This group will be created if you use ProSafe-RS in
domain environment.
User group for the users with privileges of system
configuration and system maintenance. The users for
PSF_ ProSafe-RS maintenance can be added to this group.
Manual Auto
MAINTENANCE When the Standard Model security type is selected, the
user who performs the security setting will be automatically
registered to this group.
This group has the same privilege as PSF_MAINTENANCE.
If domain environment encounters abnormality and no
one can logon to the domain, this local group can be used.
This group will be created if you use ProSafe-RS in domain
PSF_
environment. When the Standard Model security type is
MAINTENANCE_ Auto -
selected in the windows domain environment, the user who
LCL
performs the security setting will be automatically registered
to this group. When no one can logon to the domain, the user
in this group can logon to the SENG and maintain ProSafe-
RS.
PSF_UTL (*1) Manual Auto
Auto: Automatically created by Security Setting Utility
Manual: Manually created by users
- : Not used
*1: This group is prepared for the user accounts of the tool which is only used by the Yokogawa maintenance personnel.
IMPORTANT
ProSafe-RS Security Setting Utility will set the privileges for accessing folders and registries in
accordance with the user groups. These user groups should not be used for the purposes other
than the purposes instructed in this document or other ProSafe-RS User Manuals.

n Setting Items for Each Security Type

The setting items of each security type are shown below. The privileges for accessing the
folders and registries are defined in accordance with the user groups of the ProSafe-RS.
Table Security Settings and Security Types

Security Type Windows Domain Stand alone
Legacy Model
Security Setting (Standard Model) (Standard Model)
Create User Groups No (*1) Yes No
Access Privilege for Files and Folders Yes Yes Yes (*2)
Access Privilege for Registries Yes Yes Yes (*2)
Access Privilege for the Start Menu Yes Yes No
Configure DCOM Yes Yes Yes (*2)
Configure Firewall Yes Yes Yes (*3)
Yes: Will be set by Security Setting Utility
No: Will not be set by Security Setting Utility.
*1: Manually register the groups on domain controller server.

*2: Security settings will be performed by granting Full Control permission to Everyone.
*3: Turn off the firewall.
n Notices when Choosing Standard Model of Security Settings

When choosing stand model of security settings, the following items need to be noticed.
l Integration with CENTUM

When integrating with the CENTUM VP
When integrating the R2.01 or later version of ProSafe-RS with CENTUM VP, the PC can
be hardened only with R4.01 or later version of CENTUM VP. In this case, the PC hardening
needs to be performed on both ProSafe-RS and CENTUM VP during installations.
When integrating with the R3.08 or earlier version of CS 3000
The PC hardening cannot be applied. When installing ProSafe-RS, the legacy model of PC
hardening should be selected on Security Setting Utility.
l Starting of SCS Simulator by Administrative Users

In Windows Vista, no administrative user (user who belongs to Administrators group) except
the account of Administrator can start SCS Simulator. The administrative users who belong to
PSF_MAINTENANCE and PSF_MAINTENANCE_LCL groups cannot start the SCS Simulator,
so an account that does not belong to these two groups should be used to use the SCS
Simulator.
In Windows XP and Windows Server 2003, there is no restriction for starting the SCS Simulator.

<2. Confirmation of Hardware Setup> 2-1
2. Confirmation of Hardware Setup

This chapter describes how to set up the following hardware before installing the
ProSafe-RS software.
SCS
A general-purpose PC to be used as a SENG
SEE
ALSO For the explanation of how to set up the hardware when a bus converter and a communication gateway are used,
see the following:
CS 1000/CS 3000 Communication Devices (IM 33Y06H01-01E)
CENTUM VP Communication Devices (IM 33M50D10-40E)
CAUTION
Protection measures against static electricity must be taken when removing and mounting the
cards in order to set dip switches or for other purposes.
SEE
ALSO For the prevention of static electricity, see the following:
7.1, Routine Maintenance of Safety Control Unit of the Safety Control Stations (Hardware) (IM 32S06C10-
21E)
IM 32S01C50-21E 3rd Edition : Dec.22,2009 -00

<2.1 Hardware Setup for SCS> 2-2
2.1 Hardware Setup for SCS

The V net addresses of an SCS are set with a processor module.
n Processor Module Configuration

The figures below show the front and rear sides of the processor modules.
Switches for setting the domain number and station number can be found on the rear side of the
processor module. Set the numbers by removing the processor module from the safety control
unit.
l SCP401
Front Behind front cover Rear
SCP401 SCP401
RCV 1 2 RCV 1 2
SND 1 2 SND 1 2
SYNC
1 2 3 4 5 6 7 8
HRDY RDY CTRL
SCTY
COPY
SYNC
1 2 3 4 5 6 7 8
HRDY RDY CTRL
SCTY
COPY LED display
BUS1 BUS1 V net connector

Bus 1
BUS2 BUS2 V net connector

Bus 2 Station address setting switch
0
1
P 0 0 MSB LSB
DOMAIN NO.
For domain number
START/STOP switch
P MSB
STATION NO.
START
For station number
START /STOP
LSB
/STOP
BATTERY PORT
Front setting switch

ON
ON
BATTERY DOM
OFF OFF ST A
ON OFF
(6-bit DIP switch)
Battery ON/OFF switch
CN1
Maintenance connector
CN2
BATTERY LIFE
(AVE.ROOM TEMP 30C MAX.)
Battery
Battery expiration date label

020101E.ai
Figure SCP401 Processor Module

l SCP461
LED display
Vnet/IP connector
Bus 1
Vnet/IP connector Station address setting switch

Bus 2
For domain number

START/STOP switch
Front setting switch For station number

(6-bit dipswitch)
Battery
BATTERY LIFE
(AVE.ROOM TEMP 30 C MAX.)
Maintrnance Connector (Facing Down)

020105E.ai
Figure SCP461 Processor Module (for Vnet/IP)
l SCP451
SCP451 SCP451
RCV 1 2 RCV 1 2
SND SND 1 2
LED display
1 2
SYNC SYNC
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
HRDY RDY CTRL COPY HRDY RDY CTRL COPY
VNET/IP VNET/IP
BUS1 BUS1 Vnet/IP connector

Bus 1
BUS2 BUS2
Vnet/IP connector
Bus 2 Station address setting switch
0
1
P 0 MSB -
DOMAIN NO.
For domain number

LSB
START/STOP switch
P MSB
STATION NO.
For station number

START
-
START /STOP FIX

LSB
/STOP BATTERY PORT
Front setting switch

ON
ON DOMN
BATTERY STA
OFF OFF
ON OFF
(6-bit dipswitch)
CN1
Maintenance connector
CN2
BATTERY LIFE
(AVE.ROOM TEMP 30 C MAX.)
Battery

020104E.ai
Figure SCP451 Processor Module (for Vnet/IP)

n Domain Number Setting

A domain refers to a collection of stations that are connected via a single V net system.
Specify a domain number in the range from 1 to 31 (1 to 16 in the case of CENTUM integration
structure).
Set the dip switches as shown in the table below to adjust to the required domain number.
Bit numbers 2 and 3 are always 0.
0
1
Domain number parity (1 bit, odd parity)
P 0 0
1 2 3 4 5 6 7 8
Fixed to 0
MSB
Domain number
LSB
(The figure shows an example where

the domain number is set to 5.)
Bit number
MSB: Most Significant Bit
L SB: Least Significant Bit
020102E.ai
Figure Dip Switches for Setting Domain Number
Table Domain Numbers and Positions of Setting Switches

Domain
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
number
Bit number 1 0 0 1 0 1 1 0 0 1 1 0 1 0 0 1 0
Bit number 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Bit number 5 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0
Bit number 6 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0
Bit number 7 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0
Bit number 8 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
Domain
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
number
Bit number 1 1 1 0 1 0 0 1 1 0 0 1 0 1 1 0
Bit number 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Bit number 5 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
Bit number 6 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1
Bit number 7 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1
Bit number 8 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
Dip switch settings

0: Means flipping a dip switch down to the left side when looking at the module as shown in the figure above.
1: Means flipping a dip switch down to the right side when looking at the module as shown in the figure above.

n Station Number Setting

Specify a station number in the range from 1 to 64.
Set the dip switches as shown in the table below to adjust to the required station number.
0
1
Station number parity (1 bit, odd parity)
P
1 2 3 4 5 6 7 8
MSB
Station number
LSB
(The figure shows an example where

the station number is set to 10.)
Bit number
MSB: Most Significant Bit
L SB: Least Significant Bit
020103E.ai
Figure Dip Switches for Setting Station Number
Table Station Numbers and Positions of Setting Switches

Station number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Bit number 1 0 0 1 0 1 1 0 0 1 1 0 1 0 0 1 0
Bit number 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit number 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Bit number 5 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0
Bit number 6 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0
Bit number 7 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0
Bit number 8 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
Station number 17 18 -------- 30 31 32 33 - - - - - - - - - - - - - 60 61 62 63 64

Bit number 1 1 1 1 0 0 1 1 0 0 1 0
Bit number 2 0 0 0 0 0 0 0 0 0 0 1
Bit number 3 0 0 0 0 1 1 1 1 1 1 0
Bit number 4 1 1 1 1 0 0 1 1 1 1 0
-------- -------------
Bit number 5 0 0 1 1 0 0 1 1 1 1 0
Bit number 6 0 0 1 1 0 0 1 1 1 1 0
Bit number 7 0 1 1 1 0 0 0 0 1 1 0
Bit number 8 1 0 0 1 0 1 0 1 0 1 0
Dip switch settings

0: Means flipping a dip switch down to the left side when looking at the module as shown in the figure above.
1: Means flipping a dip switch down to the right side when looking at the module as shown in the figure above.

<2.2 Hardware Setup for General-purpose PC> 2-6
2.2 Hardware Setup for General-purpose PC

This section explains the hardware setup for general-purpose PCs.
Control bus interface card (VF702): For PCI Express bus
Control bus interface card (VF701): For PCI bus
TIP
If an Ethernet card needs to be added, install the Ethernet card and Ethernet driver, and then connect the PC
onto the network using an appropriate cable.
SEE
ALSO For the hardware setup of the Vnet/IP interface card (VF702/VF701), see the following:
3.4.1, Setup and Check Hardware (for Vnet/IP)

2.2.1 Address Setting of Control Bus Interface Card

A VF702/VF701 card is a control bus interface card that is mounted in a slot of a general-purpose
PC, thereby connecting the PC to the control bus.
A station address of the V net is determined as a combination of a domain number and station
number.
Dip switches for setting the domain number and station number can be found on the printed
circuit board of the VF702/VF701 card. The DIP switches are in the same locations on the VF702
and VF701 cards.
DIP switches
SW1 DOMAIN
DOM Domain number
STATION
SW2
STN Station number
020201E.ai
Figure Position of Dip Switches (VF702)
The following switches are needed to set a domain number and station number.
SW1 DOMAIN SW2 STATION
Bit number
2
1
6
7
6
7
5
8
4
4
2
P 0 0 MSB LSB P MSB LSB
Dip switches for Dip switches for

setting domain number setting station number
020202E.ai
Figure Dip Switches for Setting Station Address

l Domain Number Setting
Set the domain number to 1 if the system has only one domain.
A domain refers to a collection of stations that are connected via the V net.
Specify a domain number in the range from 1 to 31 (1 to 16 in the case of CENTUM integration
structure).
Set the dip switches as shown in the table below to adjust to the required domain number.
Bit numbers 2 and 3 are always 0.
P 0 0 MSB LSB
1 Bit number
1
2
3
4
5
6
7
8
0
Domain number (5 bits) (An example where the address Domain Number 6)
Fixed to 0
MSB: Most Significant Bit (highest-order bit)

LSB: Least Significant Bit (lowest-order bit)
020203E.ai
Figure Dip Switches for Setting Domain Number
Table Domain Numbers and Positions of Setting Switches
Domain Dip switch bit number Domain Dip switch bit number
number 1 2 3 4 5 6 7 8 number 1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1 17 1 0 0 1 0 0 0 1
2 0 0 0 0 0 0 1 0 18 1 0 0 1 0 0 1 0
3 1 0 0 0 0 0 1 1 19 0 0 0 1 0 0 1 1
4 0 0 0 0 0 1 0 0 20 1 0 0 1 0 1 0 0
5 1 0 0 0 0 1 0 1 21 0 0 0 1 0 1 0 1
6 1 0 0 0 0 1 1 0 22 0 0 0 1 0 1 1 0
7 0 0 0 0 0 1 1 1 23 1 0 0 1 0 1 1 1
8 0 0 0 0 1 0 0 0 24 1 0 0 1 1 0 0 0
9 1 0 0 0 1 0 0 1 25 0 0 0 1 1 0 0 1
10 1 0 0 0 1 0 1 0 26 0 0 0 1 1 0 1 0
11 0 0 0 0 1 0 1 1 27 1 0 0 1 1 0 1 1
12 1 0 0 0 1 1 0 0 28 0 0 0 1 1 1 0 0
13 0 0 0 0 1 1 0 1 29 1 0 0 1 1 1 0 1
14 0 0 0 0 1 1 1 0 30 1 0 0 1 1 1 1 0
15 1 0 0 0 1 1 1 1 31 0 0 0 1 1 1 1 1
16 0 0 0 1 0 0 0 0
Dip switch settings

0: Means flipping a dip switch down to the lower side when looking at the module as shown in the figure above.
1: Means flipping a dip switch down to the upper side when looking at the module as shown in the figure above.

l Station Number Setting
Specify a station number in the range from 1 to 64.
Set the dip switches as shown in the table below to adjust to the required station number.
P MSB LSB
1 Bit number
1
2
3
4
5
6
7
8
0
Station number (7 bits) (An example where the address Station Number 60)
MSB: Most Significant Bit (highest-order bit)

LSB: Least Significant Bit (lowest-order bit)
020204E.ai
Figure Dip Switches for Setting Station Number
Table Station Numbers and Positions of Setting Switches
Station Dip switch bit number Station Dip switch bit number
number 1 2 3 4 5 6 7 8 number 1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1 22 0 0 0 1 0 1 1 0
2 0 0 0 0 0 0 1 0 23 1 0 0 1 0 1 1 1
3 1 0 0 0 0 0 1 1 24 1 0 0 1 1 0 0 0
4 0 0 0 0 0 1 0 0 25 0 0 0 1 1 0 0 1
5 1 0 0 0 0 1 0 1 26 0 0 0 1 1 0 1 0
6 1 0 0 0 0 1 1 0 27 1 0 0 1 1 0 1 1
7 0 0 0 0 0 1 1 1 28 0 0 0 1 1 1 0 0
8 0 0 0 0 1 0 0 0 29 1 0 0 1 1 1 0 1
9 1 0 0 0 1 0 0 1 30 1 0 0 1 1 1 1 0
10 1 0 0 0 1 0 1 0 31 0 0 0 1 1 1 1 1
11 0 0 0 0 1 0 1 1 32 0 0 1 0 0 0 0 0
12 1 0 0 0 1 1 0 0 33 1 0 1 0 0 0 0 1
13 0 0 0 0 1 1 0 1 .. ..
.. ..
14 0 0 0 0 1 1 1 0 .. ..
.. ..
15 1 0 0 0 1 1 1 1 .. ..
. .
16 0 0 0 1 0 0 0 0
17 1 0 0 1 0 0 0 1 60 1 0 1 1 1 1 0 0
18 1 0 0 1 0 0 1 0 61 0 0 1 1 1 1 0 1
19 0 0 0 1 0 0 1 1 62 0 0 1 1 1 1 1 0
20 1 0 0 1 0 1 0 0 63 1 0 1 1 1 1 1 1
21 0 0 0 1 0 1 0 1 64 0 1 0 0 0 0 0 0
Dip switch settings

0: Means flipping a dip switch down to the lower side when looking at the module as shown in the figure above.
1: Means flipping a dip switch down to the upper side when looking at the module as shown in the figure above.

2.2.2 Mounting a Control Bus Interface Card

This section explains how to mount a VF702/VF701 card in a general-purpose PC.
SEE
ALSO The explanation here is provided assuming the use of common general-purpose PCs; please see the manual of
the actual PC to be used when mounting a VF702/VF701 card.
n Precautions on Mounting/Removing VF702/VF701 Card

Mount the VF702/VF701 card in the PC after installation and setup of Windows are
completed but before setting the network.
Install the driver of the VF702/VF701 card when restarting the PC after mounting the VF702/
VF701 card. Follow the explanation in this manual for the installation procedure.
SEE
ALSO For the procedure to install the driver of theVF702/VF701 card in a PC, see the following:
3.2, New Installation of Control Bus Driver
n VF702/VF701 Card Installation Procedure

1. Set the station address on the VF702/VF701 card.
2. Turn off the power of the PC. For safety, remove the power plug from the outlet.
3. Remove the cover of the PC.
4. Insert the VF702/VF701card in the corresponding slot and fix it to the slot.
5. Put back the cover of the PC.
6. Write the station address on the label that comes with the VF702/VF701 and stick it on the
front or another easy-to-see location of the PC.
SEE
ALSO For the explanation about how to set a station address, see the following:
2.2.1, Address Setting of Control Bus Interface Card
For the sticker on which the station address is written, see the following:
6.5, Attaching the V net Station Address Label of the Safety Control Stations (Hardware) (IM 32S06C10-
21E)

<3. Windows and Network Setup on General-purpose PC> 3-1
3. Windows and Network Setup on

General-purpose PC
This chapter explains the Windows settings required for a general-purpose PC on which
the ProSafe-RS software is installed. For each Windows operating system, the following
topics will be explained.
Settings after Windows installation
Installation of control bus driver
Network setup in Windows
Complete the installation of Windows, Service Pack and security patches before
embarking on the tasks explained in this chapter.
Also complete the setup at the domain controller PC when using the ProSafe-RS PCs in
the Windows domain environment.
n Preparation before Setup

The following explains items to be determined and preparations required before starting the
Windows setup procedure.
l Computer Name (Station Name)
IMPORTANT
Make sure that the computer name and station name match. If the computer name and station
name are different, the correct operation of ProSafe-RS cannot be guaranteed.
A computer name refers to a name used to identify each computer on a Windows network. An
arbitrary name can be specified in Control Panel of Windows.
A station name is a name determined uniquely by the control bus address in a ProSafe-RS
system.
Example: STN0164
(STNddss: dd is a domain number, ss is a station number. The same rule applies
in the following explanation as well.)

l IP Address
IP address refers to a computer address determined on a control bus and Ethernet network,
respectively.
Network addresses on a control bus and Ethernet network must have different subnets.
Example: 172.16.1.64 (control bus)
172.17.1.64 (Ethernet)
IMPORTANT
Use the same domain number.station number combination as the control bus address for the IP
address of the control bus driver of each PC.
Example: 172.16.dd.ss
Note that dd.ss must not overlap with the addresses of the other stations. In particular, it must not
overlap with the domain number.station number used in SCS and FCS.
Specify a domain number in the range from 1 to 31 and a station number from 1 to 64.
l Subnet Mask
This information identifies a network and computer in the same way as for an IP address in a
control bus or Ethernet network.
Example: 255.255.0.0
IMPORTANT
Take the following precautions when setting the IP address and subnet mask in order to connect
to an Ethernet network.
If ProSafe-RS is connected to an existing Ethernet environment, use the IP address and
subnet mask values used in the network environment for the corresponding values for the
Ethernet setting.
When constructing a new local network environment for ProSafe-RS, use the default IP
address (172.17.dd.ss) and subnet mask (255.255.0.0) that are determined by the station
address.
Use the default values (172.16.dd.ss and subnet mask of 255.255.0.0) for the IP address of a
control bus network.
l Administrators Password
It could be the case that a password has not been set for the Administrator account. The
administrator of the system must first check whether or not the password is set and, if not, set
a password. On a Windows Vista PC, logging on to the Administrator account is disabled. The
administrative user is the user that was created at the time when Windows Vista was installed.
Set a password for this user account.

n When Using Windows Server 2003/Windows Server 2008

When using a server PC, install Windows Server 2003 or Windows Server 2008.
l Setup When Installing Windows Server

When the hardware setup is completed, install Windows Server 2003 or Windows Server 2008 to
this server PC.
The setting items are as follows:
SEE
ALSO For more information about the installation procedure of Windows Server 2003/Windows Server 2008, see the
following:
Installation Guide that came with the CD-ROM for Windows Server 2003/Windows Server 2008.
Specify the following items.

License Mode
The license mode regarding the number of devices or the number of the clients needs to be
specified according to the purchased licenses.
Server type
Confirm that the server type was specified as File Server during the first time installation.

<3.1 Windows Setup> 3-4
3.1 Windows Setup

This section explains Windows settings that should be carried out before installing the
ProSafe-RS software. It is assumed that Windows, Service Pack and required security
patches have already been installed.
For each Windows operating system, the required setups for Windows will be explained.

3.1.1 Windows Setup (Windows Vista/Windows Server 2008)

In this section, the required Windows settings for installing the ProSafe-RS software in
the PC of Windows Vista/Windows Server 2008 will be explained.
The administrative user account that installed the operating system should be used for
the setups of Windows.
n Settings Related to File System

If the hard disk for installing the ProSafe-RS software is formatted with FAT, it is necessary to
reinstall the operating system and reformat the hard disk with NTFS. The partitions other than the
system partition should also be formatted with NTFS.
SEE
ALSO For more information and detailed procedure, see the following:
n Settings Related to File System in 3.1.2, Windows Setup (Windows XP/Windows Server 2003)
n Windows Hotfix Programs Installation

When the computer of Windows Vista SP1 is turned on for extended periods of time, due to
kernel virtual addresses fragmentation, some applications may not start properly and an error
message may be displayed as follows:
XXXXXX.EXE is not a valid Win32 application.
See: <http://support.microsoft.com/?kbid=952709>
In order to avoid this problem, a hotfix program is included in the ProSafe-RS CD-ROM. On a PC
with Windows Vista SP1, it is necessary to update your system using this hotfix program. The
path of the program is:
<CD-ROM Drive>:\COMMON_MS\KB952709\Vista\Windows6.0-KB952709-x86.msu
IMPORTANT
You dont need to install Hotfix KB952709 for a PC in which the CENTUM VP software is installed
because Hotfix KB952709 is already applied. If you try to install the hotfix program on such PCs,
the following message will be displayed: The update does not apply to your system. Then, click
the [OK] button to finish.

n Power Management
How to setup power management will be explained below.
1. Logon to an administrative user account.
2. Select [Control panel] from Start menu and Select [Power Options].
3. In the [Preferred plans], select [High performance] option button. After that, click [Change
plan settings].
030110E.ai
Figure Change Plan Settings
4. Choose [Never] for [Turn off the display] setting.

5. Choose [Never] for [Put the computer to sleep] setting.
6. Click [Change advanced power settings] so as to display a dialog box for setting the power
options. Conforming to the difference of PC components, the item may not be displayed. In
this case, the setting is unnecessary because the function is invalid.

7. Choose [Never] for [Turn off hard disk after] setting.
030111E.ai
Figure Hard Disk Setting
8. Choose [Never] and [Off] for sleep related options.
030112E.ai
Figure Sleep Setting

9. Choose [Do nothing] for sleep button.
030113E.ai
Figure Sleep Button Setting
10. Choose [Never] for [Turn off display after] setting.
030114E.ai
Figure Display Setting

n Disable Scheduled Disk Defragmenter Tool

Disk Defragmenter Tool can be used to reorganize the fragmented files on computer hard disk
so as to improve the computer performance. By default setting of Windows Vista, the Disk
Defragmenter Tool is scheduled to start periodically on 1:00 A.M. of Wednesday. Since the
performance of the ProSafe-RS software may be affected when defragmenter is running, it is
recommended to disable the schedule of the periodic disk defragmentation. Moreover, you can
manually start the disk defragmenter when you feel the disk performance is getting worse or
when you perform system maintenance.
The procedure to disable the schedule of disk defragmentation is as follows:
1. Logon as an administrative user.
2. Choose [Start] Menu - [All Programs] - [Accessories] - [System Tools] - [Disk Defragmenter]
so as to display Disk Defragmenter window.
030115E.ai
Figure Disk Defragmenter
3. Uncheck the option of [Run on a schedule (recommended)] and then click [OK] button.

3.1.2 Windows Setup (Windows XP/Windows Server 2003)

In this section, the required Windows settings for installing the ProSafe-RS software to
the PC of Windows XP or Windows Server 2003 will be explained.
n Settings Related to File System

In the case of a partition formatted in FAT, it is necessary to change the file system to NTFS. The
following explains how to check the file system used and how to convert it from FAT to NTFS.
1. Display the driver properties.
Right-click the local disk folder in Windows Explorer and select [Properties]. If the FAT file
system is used, perform the following procedure.
2. Display the command prompt.
Select [Programs], [Accessories] and [Command Prompt] from the [Start] menu of
Windows.
3. Enter the following command:
>CONVERT (drive name):/FS:NTFS
Example: In the case of drive C
>CONVERT C:/FS:NTFS
If the following message is displayed, enter Y and restart the PC.

Currently, it is not possible to perform conversion because exclusive access to [Drive Name]
cannot be executed with CONVERT. Do you want to schedule drive conversion at the next
system restart (Y/N)?

n System Property Setting

The following shows how to set system properties.
1. Log on as a user of the ProSafe-RS software.
2. Open the System Properties dialog box.
Select [Control Panel] and then [System] from the [Start] menu of Windows.
3. Open the Performance Options dialog box.
In the [Advanced] tab, click the [Settings] button in the [Performance] setting area.
4. Make settings in the following tab.
l [Visual Effects] Tab

Check the option [Adjust for best performance].
Performance Options ?
Visual Effects Advanced
Select the settings you want to use for the appearance and
performance of Windows on this computer.
Let Windows choose what's best for my computer

Adjust for best appearance
Adjust for best performance
Custom:
Animate windows when minimizing and maximizing

Fade or slide menus into view
Fade or slide ToolTips into view
Fade out menu items after clicking
Show shadows under menus
Show shadows under mouse pointer
Show translucent selection rectangle
Show window contents while dragging
Slide open combo boxes
Slide taskbar buttons
OK Cancel Apply
030101E.ai
Figure [Visual Effects] Tab

n Virtual Memory Setting

When coexists with CENTUM VP, the setting should be done according to the instruction of
CENTUM VP. Otherwise, the recommended virtual memory size is larger than 512 MB. If the
main memory is larger than 512 MB, it is recommended to set the virtual memory size larger than
the main memory size.
The setting procedure is shown as follows.
1. Log on as Administrator.
2. Open the System Properties dialog box.
Select [Control Panel] and [System] from the [Start] menu of Windows.
3. Open the Performance Options dialog box.
On the [Advanced] tab, click the [Settings] button of [Performance] setting area.
4. Make settings in the following tab.
l [Advanced] Tab
Make settings in the [Paging file size for selected drive] section. Set the same value for the Initial
size and Maximum size fields.
Virtual Memory
Drive [Volume Label] Paging File Size (MB)

C: 2046-4092
D:
Paging file size for selected drive

Drive: C:
Space available: 70752 MB
Custom size:
Initial size (MB): 2046
Maximum size (MB): 4092
System managed size
No paging file Set
Total paging file size for all drives
Minimum allowed: 2 MB
Recommended: 3069 MB
Currently allocated: 2046 MB
OK Cancel
030102E.ai
Figure [Advanced] Tab

n Power Management
The following shows how to set power management.
1. Log on as Administrator (account for administrators).
2. Select [Control Panel] and [Power Options] from the [Start] menu to open the [Power
Options Properties] dialog box.
3. Confirm that the settings in the following tab are as follows.
Some items may not be displayed depending on the configuration of the PC. Such inactive
items indicate that the corresponding function is not available and there is no problem.
l [Power Schemes] Tab

System standby and System hibernates must be disabled.
Turn off monitor: Never
Turn off hard disks: Never
System standby: Never
System hibernates: Never
Power Options Properties
Power Schemes Advanced Hibernate UPS
Select the power scheme with the most apropriate settings for
this computer. Note that changing the settings below will modify
the selected scheme.
Power schemes
Home/Office Desk
Save As... Delete
Setting for Home/Office Desk power scheme
Turn off monitor: Never
Turn off hard disks: Never
System standby: Never
System hibernates: Never
OK Cancel Apply
030103E.ai
Figure [Power Schemes] Tab

l [Advanced] Tab
Some PC keyboards have a sleep button. Disable the operation when this button is pressed by
the setting of [Power buttons].
When I press the sleep button on my computer: Do nothing
Select the power-saving settings you want to use.
Options
Always show icon on the taskbar
Prompt for password when computer resumes from standby
Power buttons
When I press the power button on my computer:

Shut down
OK Cancel Apply
030104E.ai
Figure [Advanced] Tab
l [Hibernate] Tab
Do not check the option [Enable hibernation].
When you computer hibernates, it stores whatever it has in

memory on your hard disk and then shuts down. When your
computer comes out of hibernation, it returns its previous state.
Hibernate
Enable hibernation
Disk space for hibernation
Free disk space: 22,057 MB

Disk space required to hibernate: 256 MB
OK Cancel Apply
030105E.ai
Figure [Hibernate] Tab

n Folder Option Settings

The following shows how to set folder options
2. Select [Folder Options] from the [Tools] menu of Windows Explorer to open Folder Options
dialog box.
3. Make the settings in the following tab.
l [General] Tab
Select the option [Use Windows classic folders] in the [Tasks] section.
Folder Options ?
General View File Types Offline Files
Tasks
Show common tasks in folders
Use Windows classic folders
Browse folders
Open each folder in the same window
Open each folder in its own window
Click items as follows

Single-click to open an item [point to select]
Underline icon titles consistent with my browser
Underline icon titles only when I point at them
Double-click to open an item [single-click to select]
Restore Defaults
OK Cancel Apply
030109E.ai
Figure [General] Tab

<3.2 New Installation of Control Bus Driver> 3-16
3.2 New Installation of Control Bus Driver

This section explains the procedure of a new installation of a control bus driver. Please
observe precautions and follow the procedures given in this section when installing the
control bus driver for the first time.
For the system connected by V net, after installing the V net and Ethernet (if required)
drivers, Windows network setup needs to be performed.
For the system connected by Vnet/IP, after installing the control bus and Vnet/IP open
communication drivers, Windows network setup needs to be performed.
SEE
ALSO For more information about Vnet/IP open communication driver installation procedure and Windows network
setup for the Vnet/IP connected systems, see the following:
3.4, Installation and Setup of Vnet/IP
IMPORTANT
Be sure to install the control bus driver before installing the ProSafe-RS software.
The control bus driver is included in the ProSafe-RS software CD-ROM. Use the Setup
command to perform the installation operation separately.
If a VF702/VF701 card is available, be sure to mount it before installing the control bus
driver. Whether or not the VF702/VF701 card is mounted is identified when the driver is
installed.
If the VF702/VF701 card is mounted after installing the control bus driver without mounting
the VF702/VF701 card, delete the control bus driver. Install the driver again after mounting
the VF702/VF701 card.
If the slot in which the VF702/VF701 card is mounted is to be changed, delete the control
bus driver before changing the slot. Install the driver again after changing the slot.
If the VF702/VF701 card is to be removed from the PC after installing the control bus driver
with the VF702/VF701 mounted, delete the control bus driver before you remove the card.
TIP
When coexisting with CENTUM VP, if a control bus driver that is compatible with the version of ProSafe-RS is
already installed, there will be no need to install the control bus driver again.
SEE
ALSO For more information about the compatibilities, read the following notices in the corresponding chapters
according to the versions.
9, Compatibility between Revisions and Cautionary Notes for Upgrading

n Notes on Using SCS Simulator

Before you use the SCS Simulator, you must install the control bus driver and set TCP/IP, even if
a control bus interface card (VF702/VF701 or VI702/VI701) is not connected to the PC on which
you run the SCS simulator. If you use more than one PC for the Expanded Test Functions, the
control bus driver must be installed to all the PCs.
Installation of the control bus driver should be done according to the procedure for installing the
control driver.
For the IP address for the control bus driver on each PC, set the address of control bus, domain
number (dd) .station number (ss).
Example: 172.16.dd.ss
Note that dd.ss must not overlap with the addresses of the other stations. In particular, it must not
overlap with the domain number.station number used in SCS and FCS.
Set a number from 1 to 16 as the domain number.
Set a number from 1 to 64 as the station number.

3.2.1 New Installation of Control Bus Driver (Windows Vista/

Windows Server 2008)
The procedure for newly installing the control bus driver in Windows Vista or Windows
Server 2008 environment will be explained in this section.
n Procedure for Newly Installing Control Bus Driver
IMPORTANT
Before starting installation, the permanently resided programs such as anti-virus programs
should stopped.
1. Start Windows and logon as an administrative user.

If the control bus card is already installed in the PC, the following dialog box will be
displayed.
030212E.ai
Figure Found New Hardware
2. On the Found New Hardware dialog box, click [Ask me again later].
3. Set the ProSafe-RS installation CD-ROM. If the installer of .NET or ProSafe-RS is
automatically started, you need to terminate the installer.
4. Find the Setup.exe under \COMDRV folder in the CD-ROM and run it.
5. If a User Account Control dialog box appears, click [Continue].

6. In the install/uninstall-selection dialog box that appears, select [INSTALL] and click [OK].
030213E.ai
Figure Install/Uninstall-Selection Dialog Box (Install Only)
7. In the dialog box confirming the installation, click [OK] to continue.

8. Windows Security dialog box for installing Yokogawa Network Protocol will be displayed.
030215E.ai
Figure Windows Security Dialog Box (For Yokogawa Network Protocol)
9. Do not select the option of [Always trust software from Yokogawa Electric Corporation].
Click [Install] button.

10. Windows Security dialog box for installing Yokogawa Network Adapters will be displayed.
030216E.ai
Figure Windows Security Dialog Box (For Yokogawa Network Adapters)
11. Do not check the option of [Always trust software from Yokogawa Electric Corporation].
12. A message appears indicating that the installation is complete.
030217E.ai
030217E.ai
Figure Installation Completed
TIP
If you have newly installed or deleted other devices before performing the new installation of the control bus
driver, a message requiring restarting of the PC may be displayed in the installation completion message box. In
this case, be sure to restart the PC after doing step 14.

13. Click [OK] and then remove the CD-ROM from the drive.
14. If the Set Network Location dialog box appears after a while, click [Work]. In the User
Account Control dialog box that appears, click [Continue].
030219E.ai
Figure Set Network Location
IMPORTANT
It takes about 1 minute to display the Set Network Location dialog box. Wait for the dialog
box to appear, and follow step 14.
Depending on the network status, the Set Network Location dialog box may not appear. If
it does not appear after a few minutes, skip step 14.
Even if you skip step 14 or if you click the wrong item other than [Work], they will be offset in
the network setup later.

n Confirming that the Driver is Properly Installed

After installing the driver, [Yokogawa Vnet Adapter] will be shown as a sub tree of Network
adapters in Device Manager.
Device Manger can be started from Control Panel through Start menu.
If the adapter is not working properly, an exclamation mark (!) will be displayed next to the icon of
the network adapter.
030220E.ai
Figure Network Adapter is Properly Installed

Whether the Yokogawa Vnet protocol is properly installed can be confirmed on Device Manager.
After enabling [Show hidden devices] on View menu, [Yokogawa Vnet Protocol] will be displayed
under the directory of [Non-Plug and Play Drivers]. If the protocol is not working properly, an
exclamation mark (!) will be displayed next to the icon of the protocol.
TIP
Yokogawa Vnet Protocol may not be displayed right after installing the driver. This is not an error. Choose [Scan
for hardware changes] on [Action] menu of the Device Manager, and then the protocol will be displayed.
030221E.ai
Figure Network Protocol is Properly Installed

3.2.2 New Installation of Control Bus Driver (Windows XP/

The procedure for newly installing the Control Bus driver in Windows XP or Windows
n Detailed Procedure of New Installation of Driver
IMPORTANT
Stop the operation of resident programs, including anti-virus software, if they are running, before
installation.

The following balloon appears if a control bus card is mounted.
Found New Hardware
Network Controller
11:24 AM
030202E.ai
Figure Found New Hardware (1)
2. If the Found New Hardware Wizard window appears, click the [Cancel] button.
Found New Hardware Wizard
Welcome to the Found New

Hardware Wizard
This wizard helps you install software for:
Yokogawa Vnet/Lnet Adapter
If your hardware came with an installation CD

or floppy disk, insert it now.
What do you want the wizard to do?
Install the software automatically (Recommended)

Install from a list or specific location (Advanced)
Click Next to continue.
< Back Next > Cancel
030203E.ai
Figure Found New Hardware Wizard

When you click the [Cancel] button, the following balloon appears, but this poses no problem.
Found New Hardware

A problem occurred during hardware installation.
Your new hardware might not work properly.
11:24 AM
030204E.ai
Figure Found New Hardware (2)
3. Insert the CD-ROM for installing ProSafe-RS in the drive.

4. Execute setup.exe in the \COMDRV folder in the installation CD-ROM.
Vnet Driver Setup
Welcome
This program let you install or uninstall Vnet Driver.
Choose one of the options below.
INSTALL
Install Vnet Driver to you system.
UNINSTALL
Remove installed Vnet Driver.
OK Cancle
030201E.ai
6. In the dialog box confirming the installation, click the [OK] button.
The Hardware Installation dialog box appears.
Hardware Installation
The software you are installing for this hardware:

Yokogawa Vnet Adapter
has not passed Windows Logo testing to verify its compatibility

with Windows XP. (Tell me why this testing is important.)
Continuing your installation of this software may impair

or destabilize the correct operation of your system
either immediately or in the future. Microsoft strongly
recommends that you stop this installation now and
contact the hardware vendor for software that has
passed Windows Logo testing.
Continue Anyway STOP Installation
030206E.ai
Figure Hardware Installation

7. A message notifying that proper operations are not guaranteed appears, but this poses no
problem. Click the [Continue Anyway] button.
A message appears indicating that the installation is complete.
tip
If you have newly installed or deleted other devices before performing the new installation of the control bus
driver, a message requiring restarting of the PC may be displayed in the installation completion message box. In
this case, be sure to restart the PC.
8. Click the [OK] button and remove the CD-ROM.

9. A balloon notifying [New network device installed] appears. Close the balloon by clicking the
[X] button in the upper right corner. Do not start Network Setup Wizard.
If you started Network Setup Wizard, click the [Cancel] button.
New network device installed

Windows has detected the installation of a new networking
device. If you want to set up a network, click here to run the
Network Setup Wizard.
030209E.ai
Figure Installation Completion of New Network Device


When the driver is newly installed, a device labeled [Yokogawa Vnet Adapter] appears among
the network adapters in Device Manager. Device Manager can be opened by selecting [Device
Manager] in the tree on the left panel of the Computer Management window, which is opened by
clicking the [Manage] menu from the menu displayed by right-clicking the [My Computer] icon.
If the driver does not start up normally, an exclamation mark (!) is displayed next to the [Network
Adapter] icon.
Computer Management
File Action View Window Help
Computer Management (Loal) HIS0164

System Tools Computer
Event Viewer Disk drives
Shared Folders Display adapters
Local Users and Groups DVD/CD-ROM drives
Performance Logs and Alerts Floppy disk controllers
Device Manager Floppy disk drives
Storage Human Interface Devices
Removable Storage IDE ATA/ATAPI controllers
Disk Defragmenter Keyboards
Disk Management Mice and other pointing devices
Services and Applications Monitors
Network adapters
Broadcom NetXtreme 57xx Gigabit Controller
Ports (COM & LPT)
Processors
Sound, video and game controllers
System devices
Universal Serial Bus controllers
Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
030210E.ai

To check the protocol driver, enable [Show hidden devices] in the [View] menu to display the
[Yokogawa Vnet Protocol] driver under [Non-Plug and Play Drivers].
If the driver does not start up normally, an exclamation mark (!) is displayed next to the [Non-Plug
and Play devices] icon.
TIP
Yokogawa Vnet Protocol may not be displayed right after installing the driver. This is not an error. Choose [Scan
for hardware changes] on [Action] menu of the Device Manager, and then the protocol will be displayed.
Computer Management
Computer Management (Loal) Non-Plug and Play Drivers

System Tools AFD Networking Support Environment
Event Viewer Beep
Shared Folders Diskperf
Local Users and Groups dmboot
Performance Logs and Alerts dmload
Device Manager Fs_Rec
Storage Generic Packet Classifier
Removable Storage IPSEC driver
Disk Defragmenter KSecDD
Disk Management mnmdd
Services and Applications mountmgr
NDIS System Driver
NDProxy
NetBios over Tcpip
NetDetect
Null
partmgr
ParVdm
Remote Access Auto Connection Driver
Remote Access IP ARP Driver
TCP/IP Protocol Driver
vga
VgaSave
Yokogawa Vnet Protocol
030211E.ai
Figure Network Protocol is Properly Installed

<3.3 Windows Network Setup> 3-29
3.3 Windows Network Setup

This section explains the network settings of Windows. Perform the tasks explained in
this section after installing the Ethernet driver and control bus driver.
Here, how to setup the networks in Windows Vista/Windows Server 2008 environment and
Windows XP/Windows Server 2003 environment will be explained respectively.
SEE
ALSO For more information about the PC network setups connected by Vnet/IP, see the following accordingly:
3.4.5, Setting Vnet/IP Network Connection (Windows Vista/Windows Server 2008)
3.4.6, Setting Vnet/IP Network Connection (Windows XP/Windows Server 2003)
IMPORTANT
The network bridge connection should not be created for ProSafe-RS system. This may cause
malfunction of control bus communication. If a bridge is already created, it must be deleted.

3.3.1 Setting Network Connection (Windows Vista/Windows

Server 2008)
In this section, how to set the network connection in Windows Vista/Windows Server 2008
PC will be explained.
n Procedure 1 Change Local Area Connection Names

The local area connection name must be changed.
The purpose of changing the local area connection name is for easily identifying the network.
1. Start [Control Panel] from Start menu and choose [Network and Internet] - [Network and
Sharing Center] from Control Panel.
030313E.ai
Figure Network and Sharing Center

2. Choose [Manage Network Connections] and then a dialog box with network connections will
be displayed.
If the drivers for the network devices are properly running, Local Area Connection is
displayed for each of the network devices in the order their drivers were installed. If a
device is not displayed here, the device or the device driver may not be properly installed or
encounters some malfunctions. Troubleshooting needs to be performed until the device is
properly displayed here.
030314E.ai
Figure Network Connection
3. Since Ethernet and Control Bus drivers are already installed, there are two connections,
[Local Area Connection] and [Local Area Connection 2] in the window. Since the two names
are not easily distinguishable, you need to change the connection names.
4. Right-click the [Local Area Connection] that corresponds to the Ethernet, and then choose
[Rename] from the menu. And then change the name to Ethernet.
5. The connection that corresponds to Control Bus card is displayed and described as
Yokogawa Vnet Adapter. Right-click its icon, for example [Local Area Connection 2], and
choose [Rename] from the menu and change its name to Vnet.
030315E.ai
Figure Network Connections (Renamed)

n Procedure 2 Setting IP Addresses

In Windows, use of DHCP is enabled by default when a network driver is installed. Since the
standard setting of ProSafe-RS does not use DHCP, the IP addresses must be set explicitly.
Set the IP addresses respectively for both the Ethernet and control bus networks. Note that this
setting must be made even when the PC is used in a domain environment.
l Ethernet IP Address
1. On the window of Network Connection, right click the icon of Ethernet, and choose
[Properties] from the menu so as to display the Ethernet Properties window.
030316E.ai
Figure Ethernet Properties
2. Set the check marks only for the following items in the area of [This connection uses the
following items].
Client for Microsoft Network
QoS Packet Scheduler
File and Printer Sharing for Microsoft Network
Internet Protocol Version 4 (TCP/IPv4)
Link-Layer Topology Discovery Mapper I/O Driver
Link-Layer Topology Discovery Responder
IMPORTANT
The option of [Internet Connection Sharing] in [Sharing] tab of Ethernet Properties window
should not be enabled.

3. Choose [Internet Protocol Version 4 (TCP/IPv4)] and then click [Properties].
030317E.ai
Figure Internet Protocol Version 4 (TCP/IPv4) Properties (Ethernet)
4. Check [Use the following IP address] and set as follows:

When using the existing setting
Enter the currently used IP address of the network environment.
When using the new setting in the new environment,
Set the IP address in accordance with the PC station address defined for the ProSafe-RS
system.
The rule is as follows:
IP address: 172.17.<Domain Number>.<Station Number> (*1)
Subnet mask: 255.255.0.0
Default gateway: No setting is required
*1: Generally use this rule to set the IP address. However, the IP address other than this rule can also be used.
No need to restart the PC after setting the IP address.
IMPORTANT
For Windows workgroup environment, do not set or change the DNS server address and
any of the settings accessed by clicking the [Advanced] button.
For Windows domain environment, set the DNS server address used by the Windows
domain server.

l Control Bus IP Address
1. On the window of Network Connection, right click the icon of Vnet, and choose [Properties]
from the menu so as to display the Vnet Properties window.
030318E.ai
Figure Vnet Properties
2. Check the protocols below in [This connection uses the following items:]. Only the protocols
listed below should be checked. Other protocols must be unchecked.
IMPORTANT
The option of [Internet Connection Sharing] in [Sharing] tab of Vnet Properties window should
not be enabled.

3. Choose [Internet Protocol Version 4(TCP/IPv4)] and then click [Properties].
030319E.ai
Figure Internet Protocol Version 4 (TCP/IPv4) Properties (Vnet)

Standard Setting:
system. The rule is as follows:
To avoid conflicts with the existing setting:

IP address: XXX.YYY.<Domain Number>.<Station Number> (*1)
*1: XXX.YYY stands for a subnet that is not identical with other subnet. No need to restart the PC after setting the IP address.

n Procedure 3 Bindings
In the case that the PC is installed with multiple network adapters such as Ethernet and Control
Bus adapters, the protocols and services bound to each adapter need to be defined. The
Ethernet should be placed at a higher priority than the Control Bus (Vnet).
Bindings of the adapters can be defined on Advanced Settings window by clicking [Advanced]
on the [Network Connections] window.
030320E.ai
Figure Network Connections Window
1. Click [Advanced] on Network Connections window so as to call [Advanced Settings]

window.
TIP
If the menu of [Advanced] is not displayed, press Alt key will display the menu.
030321E.ai
Figure Before Changing Connection Order

For example, if the Control Bus (Vnet) is installed later than Ethernet, the Control Bus will be at
the higher position and connected first.
2. Click the upward or downward arrows next to Connections box so as to change the Ethernet
to the higher position than Control Bus.
030322E.ai
Figure After Changing Connection Order
As shown in the above example, when Ethernet is moved to the higher position than Vnet, click
[OK] button.
After changing the connection order and bindings, there is no need to restart the PC.
IMPORTANT
Do not change the position of [Remote Access connections] so as to keep it at the lowest
position.
Do not change the items in Provider Order tab.
Do not change the bindings for Ethernet and Vnet in the Bindings box below the
Connections box.

n Procedure 4 Change Computer Name

It is recommended to use the station name of ProSafe-RS system as the computer name. The
computer name can be changed on System Properties.
1. Click [System] in [Control Panel] of Start menu. Click [Advanced system setting] so as to
open System Properties window. Then, click [Computer Name] tab.
030323E.ai
Figure System Properties

2. Click [Change] so as to display Computer Name/Domain Changes window.
030324E.ai
Figure Computer Name/Domain Changes

3. Enter the new computer name (case is irrelevant) for the PC.
4. If the PC belongs to a Windows domain, check the option [Domain] and then enter the name
of the Windows domain.
5. Click [OK]. A message box will be displayed to prompt for restarting the PC. The new
computer name will become valid after restarting the PC.
6. Restart the PC.
n Procedure 5 Set Network Location

Follow the procedure below to change the location type of the [Unidentified Networks] to
Private.
1. Choose [Control Panel] - [Administrative Tools] - [Local Security Policy] to display the Local
Security Policy window.
030330E.ai
Figure Local Security Policy
2. Choose [Network List Manager Policies] in the left pane, and then double click [Unidentified
Networks] in the right pane to open the Unidentified Networks Properties dialog box.
030331E.ai
Figure Unidentified Networks Properties

3. Select [Private] at Location type and then click [OK].
n Procedure 6 Set Network and Sharing Center

Change the settings in Network and Sharing Center. From the Start menu, select Control Panel,
then call Network and Sharing Center.
1. In the Network and Sharing Center, confirm that [(Private network)] appears for both V net
and Ethernet connections.
030325E.ai
Figure Network and Sharing Center

2. If [(Private network)] does not appear, do the following:
2-1. Click [Customize]. The Set Network Location dialog box appears.
030327E.ai
Figure Set Network Location
2-2. Click [Private] and click [Next]. [Successfully set network settings] dialog box appears. Click
[Close]. In the User Account Control dialog box that appears, click [Continue].
030328E.ai
Figure Set Network Location (Complete)

3. [Sharing and Discovery] settings should be set as follows:
In Windows Vista
Network Discovery: On
File Sharing: On
Public folder sharing: Off
Printer Sharing: On or Off (Set this option to On for connecting printers to the network.)
Password protected sharing: On
Media sharing: Off
In Windows Server 2008

Network Discovery: Custom (Custom is displayed even if you set this option to On.)
File Sharing: On
Public folder sharing: Off
Printer Sharing: On or Off (Set this option to On for connecting printers to the network.)
Password protected sharing: On

3.3.2 Setting Network Connection (Windows XP/Windows

Server 2003)
In this section, how to set the network connection in Windows XP and Windows Server
2003 PC will be explained.
n Procedure 1 Changing Local Area Connection Names

Be sure to change the names of the local area connections.
It becomes easier to identify the networks by changing the names of the local area connections.
1. Start the Network Connections window from [Control Panel] selected from the [Start] menu.
If the drivers for the network devices are properly running, Local Area Connection is
displayed for each of the network devices in the order their drivers were installed.
Network Connections
File Edit View Favorites Tools Advanced Help
Back Search Folder
Address Network Connections Go

LAN or High - Speed Internet
Network Tasks
Create a new
connection Local Area Local Area
Set up a home or small Connection Connection 2
office network
See Also
Network Troubleshooter
030301E.ai
Figure Network Connections
If some connections are not displayed here, either their installation failed or their drivers are not
running normally.
Here, [Local Area Connection] and [Local Area Connection 2] are displayed because the
Ethernet and control bus drivers have been installed. These names should be changed to more
apporpriate ones so that their corresponding connections can be identified.
2. Open the properties sheet of [Local Area Network] as well. See the indication at [Connect
using:] to make sure that this is Ethernet connection, and then close the properties sheet.
3. In the Network Connections window, right-click the [Local Area Connection] icon, choose
[Rename] from the menu displayed, and then change the name to Ethernet.
4. Open the properties sheet of [Local Area Network 2]. Make sure that Yokogawa Vnet
Adapter is indicated at [Connect using:] and close the properties sheet.

5. In the Network Connections window, right-click the [Local Area Connection 2] icon, choose
[Rename] from the menu displayed, and then change the name to Vnet.
Network Connections
File Edit View Favorites Tools Advanced Help
Back Search Folder
Address Network Connections Go

LAN or High - Speed Internet
Network Tasks
Create a new
connection Ethernet Vnet
Set up a home or small
office network
030305E.ai
Figure Network Connections (After Renaming)
n Procedure 2 Setting IP Address

standard setting of ProSafe-RS does not use DHCP, the IP addresses must be set explicitly.
Set the IP addresses respectively for both the Ethernet and control bus networks. Note that this
setting must be made even when the PC is used in a domain environment.
l IP Address of Ethernet
1. Display the Ethernet Properties dialog box from the Network Connections window.
Ethernet Properties
General Authentication Advanced
Connect using:
Intel(R) pro/100 VE Network Connectic
Configure...
This connection uses the following items:
Internet Protocol (TCP/IP)
Install... Uninstall Properties
Description
Transmission Control Protocol/Internet Protocol. The default
wide area network protocol that provides communication
across diverse interconnected networks.
Show icon in notification area when connected
OK Cancel
030306E.ai
Figure Ethernet Properties

2. Select [Internet Protocol (TCP/IP)] and click the [Properties] button.
The Internet Protocol (TCP/IP) Properties dialog box appears.
3. Select [Use the following IP address] and set the following values for IP address, subnet
mask and default gateway of Ethernet.
If the PC is used in an existing environment, specify the values used in the network
environment.
If the PC is used in a new environment, specify the default values determined by the
station address.
The default values of Ethernet are as follows:
IP address (*1): 172.17.domain number.station number
Default gateway: No specification
*1: Other IP addresses can also be used, although the use of the default IP address is standard in a new environment.
A setting example is shown below.

Internet Protocol (TCP/IP) Properties ?
General
You can get IP settings assigned automatically if your network supports

this capability. Otherwise, you need to ask your network administrator for
the appropriate IP settings.
Obtain an IP address automatically
Use the following IP address:

IP address: 172 17 1 24
Subnet mask: 255 255 0 0
Default gateway:
Obtain DNS server address automatically
Use the following DNS server addresses:

Preferred DNS server:
Alternate DNS server:
Advanced...
OK Cancel
030307E.ai
Figure Example of Ethernet IP Address Setting
In the example above, 172.17.1.24 is set for the IP address.

Enter an appropriate IP address according to the network to be connected to.
Note that it is not necessary to restart the PC even if an IP address is changed in Windows.
IMPORTANT
domain serve r.

1. On the window of Network Connection, right click the icon of Vnet, and choose [Properties]
from the menu so as to display the Vnet Properties window.
030326E.ai
Figure Vnet Properties
TIP
When settings on General tab of the properties sheet, the PC needs to be restarted.

3. Choose [Internet Protocol (TCP/IP)] and then click [Properties] so as to display the [Internet
Protocol (TCP/IP) Properties] window.
General
You can get IP settings assigned automatically if your network supports

this capability. Otherwise, you need to ask your network administrator for
the appropriate IP settings.

IP address: 172 16 1 24
Default gateway:

Advanced...
OK Cancel
030308E.ai
Figure Example of Vnet IP Address Setting
4. Select the [Use the following IP address] option and set the IP address and subnet mask of
Vnet to the default values that are determined according to the station address.
IMPORTANT
Do not set the default gateway.
Standard Setting:


n Procedure 3 Network Bindings

If multiple network cards such as Ethernet and control bus cards have been installed, it is
necessary to set network bindings. Make settings such that the priority of Ethernet becomes
higher than that of the control bus (V net).
Settings related to network bindings are made in the Advanced dialog box, which can be
accessed from the Internet Protocol (TCP/IP) Properties window.
1. Select [Advanced Settings] in the [Advanced] menu of the Network Connections window.
The Advanced Settings window appears.
Advanced Settings
Adapters and Bindings Provider Order
Connections are listed in the order in which they are accessed by

network services.
Connections:
Vnet
Ethernet
[Remote Access connections]
Bindings for Local Area Connection:
File and Printer Sharing for Microsoft Networks

Client for Microsoft Networks
OK Cancel
030309E.ai
Figure Before Setting Network Bindings
In the figure above, the control bus (Vnet) has higher priority than the Ethernet network in the
connection because the control bus was installed later.

2. Set the orders with the arrow buttons displayed next to the [Connections] section to make
the Ethernet priority higher than that of the control bus (Vnet).
Advanced Settings
Connections are listed in the order in which they are accessed by

network services.
Connections:
Ethernet
Vnet
Bindings for Local Area Connection:

OK Cancel
030310E.ai
Figure Advanced Settings Dialog Box after Setting Network Bindings
3. Move the Ethernet above the control bus and click the [OK] button.
The network bindings are completed.
Note that it is not necessary to restart the PC even if the network bindings are changed in
Windows.
IMPORTANT
Do not change the priority of remote access connections (keep it the lowest as is).
It is not necessary to make any settings in the [Provider Order] tab.
Do not change the network bindings for [Ethernet] and [Vnet] displayed below the
[Connections] section.

n Procedure 4 Changing Computer Name

1. Select [Network Identification] in the [Advanced] menu at the top of the Network
Connections window.
The System Properties dialog box appears.
This dialog box can also be displayed by selecting [System] from [Control Panel].
System Properties
System Restore Automatic Updates Remote

General Computer Name Hardware Advanced
Windows uses the following information to identify your computer

on the network.
Computer description: Safty SENG No1
For example: Kitchen Computer or Marys

Computer.
Full computer name: HIS0124
Workgroup: WORKGROUP
To use the Network Identification Wizard to join a Network ID

domain and create a local user, click Network ID.
To rename this computer or join a domain, click

Change. Change...
OK Cancel Apply
030311E.ai
2. Click the [Change] button.

The [Computer Name Changes] dialog box appears.
The [Change] button is grayed out and the name cannot be changed in the case of a
domain controller.
Computer Name Changes
You can change the name and the membership of this

computer. Changes may affect access to network resources.
Computer name:
HIS0164
Full computer name:

HIS0164.
More...
Member of
Domain:
Workgroup:
WORKGROUP
OK Cancel
030312E.ai
Figure Compute Name Changes

3. Enter the computer name you want to set (case insensitive) and click the [OK] button.
A dialog box appears, prompting to restart the PC. The changed computer name becomes
valid after restarting the PC.
4. Restart the PC.

<3.4 Installation and Setup of Vnet/IP> 3-52
3.4 Installation and Setup of Vnet/IP

This section explains how to install and setup the ProSafe-RS software for Vnet/IP.
n Procedure for Applying Vnet/IP

The procedure and the detailed steps on how to apply Vnet/IP are explained below.
About Vnet/IP, the flows of work differ according to the following cases besides a setup of new
installation.
Update Vnet/IP Open Communication Driver
Delete Vnet/IP Open Communication Driver
The detailed steps are explained below.
TIP
Since Vnet/IP supports Open Communication, the Ethernet cable connection becomes unnecessary.
In this case, the onboard NIC (the network card on PC) should be disabled by any of the following methods:
Disable the card on BIOS.
Disable the network connection on its properties sheet.
Disable the card on Device Manger.
For more information about the detailed procedure, see the reference manuals of Windows.

n Overall Flow of New Installation Tasks

The following flowchart explains the overall flow of the ProSafe-RS installation tasks in a
simplified manner.
Start
See 2, Confirmation of Hardware Setup.

1. SCS hardware setup See 6.8, Installing the Vnet/IP Interface Card to a PC
of Safety Control Stations (Hardware) (IM 32S06C10-21E)
This task is not required if Windows has already

2. Windows installation been installed on a recommended PC.
3. Windows Service This task is not required if Windows Service Pack

Pack installation has already been installed on a recommended PC.
4. Windows setup See 3.1, Windows Setup.
Virtual memory setting
Apply ProSafe-RS Y
in Windows Domain
Environment ?
5. Setup Domain Environment See 12, Setting of Windows
N (on domain server) Domain Environment
6. Installing Vnet/IP interface card

See 3.4.1, Setup and Check Hardware (for Vnet/IP)
in the general-purpose PC
See 3.4.2, "Installation of Network Drivers"
See 3.4.3, "Installation of Open Communication Driver (Windows Vista/
7. Network setup Windows Server 2008)"
See 3.4.4, "Installation of Open Communication Driver (Windows XP/
Windows Server 2003)"
See 3.4.5, "Network Settings for Vnet (Windows Vista/Windows Server 2008)"
Was the original Y See 3.4.6, "Network Settings for Vnet/IP (Windows XP/Windows Server 2003)"
Windows CD-ROM used
in the task above?
8. Windows Service Pack
reinstallation
N
9. ProSafe-RS software
See 4, New Installation of ProSafe-RS Software
installation
10. Setup Information Securities See 11, Security Setting Utility
11. Electronic document setting See 4.2, Online Manual Setting
12. Settings after ProSafe-RS

See 4.3, Settings after Software Installation
installation
Create User Accounts

Define Desktop Properties
: Vnet/IP related
End
030401E.ai
Figure Flow of Installation Tasks

l Update Vnet/IP Open Communication Driver
Start
Run setup command
End
030402E.ai
Figure Updating Vnet/IP Open Communication Driver
l Delete Vnet/IP Open Communication Driver
Start
Run setup command
End
030403E.ai
Figure Deleting Vnet/IP Open Communication Driver
SEE
ALSO For more information about updating or removing Vnet/IP Open Communication Driver, see the following
respectively with each Windows OS type:
n Update or Delete Vnet/IP Open Communication Driver (Windows Vista/Windows Server 2008) in 3.4.7,
Reinstallation (For Vnet/IP)
n Update or Delete Vnet/IP Open Communication Driver (Windows XP/Windows Server 2003) in 3.4.7,
Reinstallation (For Vnet/IP)

3.4.1 Setup and Check Hardware (for Vnet/IP)

How to setup and check the hardware before installing the ProSafe-RS software used for
Vnet/IP control bus is explained below.
When setting up hardware, the DIP switches of the following devices need to be used for
setting the domain number and station number.
Vnet/IP Interface Card (VI702): For PCI Express bus
Vnet/IP Interface Card (VI701): For PCI bus
V net Router (AVR10D)
SEE
ALSO For more information about hardware details of Vnet/IP Interface Card (VI702/VI701), see the following:
6.6, Front Panel of the Vnet/IP Interface Card of the Safety Control Stations (Hardware) (IM 32S06C10-
21E)
For more information about installing the Vnet/IP Interface Card (VI702/VI701) to a PC, see the following:
6.8, Installing the Vnet/IP Interface Card to a PC of the Safety Control Stations (Hardware) (IM 32S06C10-
21E)
n Setup Vnet/IP Station Address on Control Bus

The DIP switches for setting the Vnet/IP station address can be found on the Vnet/IP Interface
Card (VI702/VI701).
The station address needs to be set before installing the ProSafe-RS software.
How to setup the station address is explained below.
l Location of VI702/VI701 DIP switches

The address on the control bus consists of domain number and station number.
On the printed circuit board of the VI702/VI701 card, the DIP switches for domain and station
numbers are located. The DIP switches are found in the same locations on the VI702 and VI701
cards.
DIP switch
Domain No. Station No.
DOMAIN
SW1
STATION
SW2
Action mode
SW4
030404E.ai
Figure Location of DIP switches (VI702)

l Setup VI702/VI701 Domain Number
Set it to 1 for a single network system.
Unless other specified, all bits are set to 0 (OFF) at shipment from the factory.
Domain is a range of stations connected by a single Vnet/IP. Set the domain number in the range
of 1 to 31. Set the DIP switches as shown in the following table to set the necessary domain
number.
Bit 2 of the DIP switch are always 0.
P 0 MSB LSB
1 Bit number
1
2
3
4
5
6
7
8
Domain number (6 bits) (An example where the address Domain Number 6)
Fixed to 0
MSB : Most Significant Bit (highest-order bit)

LSB : Least Significant Bit (lowest-order bit)
030405E.ai
Figure DIP Switches for Domain Number Setting
Table Domain Numbers and Switch Positions
Domain DIP switch bit number Domain DIP switch bit number
number 1 2 3 4 5 6 7 8 number 1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1 17 1 0 0 1 0 0 0 1
2 0 0 0 0 0 0 1 0 18 1 0 0 1 0 0 1 0
3 1 0 0 0 0 0 1 1 19 0 0 0 1 0 0 1 1
4 0 0 0 0 0 1 0 0 20 1 0 0 1 0 1 0 0
5 1 0 0 0 0 1 0 1 21 0 0 0 1 0 1 0 1
6 1 0 0 0 0 1 1 0 22 0 0 0 1 0 1 1 0
7 0 0 0 0 0 1 1 1 23 1 0 0 1 0 1 1 1
8 0 0 0 0 1 0 0 0 24 1 0 0 1 1 0 0 0
9 1 0 0 0 1 0 0 1 25 0 0 0 1 1 0 0 1
10 1 0 0 0 1 0 1 0 26 0 0 0 1 1 0 1 0
11 0 0 0 0 1 0 1 1 27 1 0 0 1 1 0 1 1
12 1 0 0 0 1 1 0 0 28 0 0 0 1 1 1 0 0
13 0 0 0 0 1 1 0 1 29 1 0 0 1 1 1 0 1
14 0 0 0 0 1 1 1 0 30 1 0 0 1 1 1 1 0
15 1 0 0 0 1 1 1 1 31 0 0 0 1 1 1 1 1
16 0 0 0 1 0 0 0 0
Setting of the DIP switch
0: The switch is flipped down in the diagram above.
1: The switch is flipped up in the diagram above.

l Setup VI702/VI701 Station Number
Set the station number in the range of 1 to 64. Set the DIP switches as shown in the following
table to set the necessary station number.
P MSB LSB
1 Bit number
1
2
3
4
5
6
7
8
0
Station number (7 bits) (An example where the address Station Number 60)
MSB : Most Significant Bit (highest-order bit)

LSB : Least Significant Bit (lowest-order bit)
030407E.ai
Figure DIP Switches for Station Number Setting
Table Station Numbers and Switch Positions

Station DIP switch bit number Station DIP switch bit number
number 1 2 3 4 5 6 7 8 number 1 2 3 4 5 6 7 8
1 0 0 0 0 0 0 0 1 22 0 0 0 1 0 1 1 0
2 0 0 0 0 0 0 1 0 23 1 0 0 1 0 1 1 1
3 1 0 0 0 0 0 1 1 24 1 0 0 1 1 0 0 0
4 0 0 0 0 0 1 0 0 25 0 0 0 1 1 0 0 1
5 1 0 0 0 0 1 0 1 26 0 0 0 1 1 0 1 0
6 1 0 0 0 0 1 1 0 27 1 0 0 1 1 0 1 1
7 0 0 0 0 0 1 1 1 28 0 0 0 1 1 1 0 0
8 0 0 0 0 1 0 0 0 29 1 0 0 1 1 1 0 1
9 1 0 0 0 1 0 0 1 30 1 0 0 1 1 1 1 0
10 1 0 0 0 1 0 1 0 31 0 0 0 1 1 1 1 1
11 0 0 0 0 1 0 1 1 32 0 0 1 0 0 0 0 0
12 1 0 0 0 1 1 0 0 33 1 0 1 0 0 0 0 1
13 0 0 0 0 1 1 0 1 .. ..
.. ..
14 0 0 0 0 1 1 1 0 .. ..
.. ..
15 1 0 0 0 1 1 1 1 .. ..
.. ..
16 0 0 0 1 0 0 0 0
17 1 0 0 1 0 0 0 1 60 1 0 1 1 1 1 0 0
18 1 0 0 1 0 0 1 0 61 0 0 1 1 1 1 0 1
19 0 0 0 1 0 0 1 1 62 0 0 1 1 1 1 1 0
20 1 0 0 1 0 1 0 0 63 1 0 1 1 1 1 1 1
21 0 0 0 1 0 1 0 1 64 0 1 0 0 0 0 0 0
030408E.ai
Setting of the DIP switch

0: The switch is flipped down in the diagram above.
1: The switch is flipped up in the diagram above.
n Setup V net Router Addresses

V net Routers should be set up on the CENTUM side.
SEE
ALSO For the explanation of how to setup DIP switches on the communication module of the V net Router, see the
following:
D6.5.3, Communication Module of CS 3000 Vnet/IP (IM 33Q06H90-31E)
D6.5.3, Communication Module of CENTUM VP Vnet/IP (IM 33L01A10-40E)

3.4.2 Installation of Network Drivers

After installing the Vnet/IP interface card (VI702/VI701), the network driver needs to be
installed. If a VF702/VF701 card is installed in the PC, remove it before installation of the
drivers.
n Network Drivers
For Vnet/IP network communications, the following drivers need to be installed.
Control Bus Driver
Vnet/IP Open Communication Driver
SEE
ALSO For more information about installing control bus driver, see the following respectively with each Windows OS
type (the procedure for Control Bus Driver is the same for VI702/VI701):
n Procedure for Newly Installing Control Bus Driver in 3.2.1, New Installation of Control Bus Driver
(Windows Vista/Windows Server 2008)
n Detailed Procedure of New Installation of Driver in 3.2.2, New Installation of Control Bus Driver
(Windows XP/Windows Server 2003)
How to setup Vnet/IP Open Communication Driver is explained below:
n Procedure of Installing Driver

The procedure for installing Vnet/IP Open Communication Driver is as follows:
Start
Run setup command
End
030409E.ai
Figure Installing Vnet/IP Open Communication Driver

l Cautions on Installing Vnet/IP Open Communication Driver
After installing the VI702/VI701 card, Vnet/IP Open Communication driver for VI702/VI701 card
must be manually installed.
IMPORTANT
When installing this driver, the installation program will look for the VI702/VI701 Vnet/IP
interface card first. For applying VI702/VI701, the VI702/VI701 card must be inserted before
installing the driver.
When changing the slot for the VI702/VI701 card, it is necessary to uninstall the Vnet/IP
Open Communication Driver beforehand. And reinstall the driver after the slot change is
completed.
When removing a VI702/VI701 card from the PC, it is necessary to uninstall the Vnet/IP
Open Communication Driver beforehand.
The setup command does not configure the IP address. It is necessary to setup the network
separately.

3.4.3 Installation of Open Communication Driver (Windows

Vista/Windows Server 2008)
The procedure for installing the Open Communication driver in a Windows Vista or
Windows Server 2008 environment will be explained in this section.
n Detailed Procedure of Installing Open Communication Driver
IMPORTANT
Before starting installation, the permanently resided programs such as anti-virus programs
should stopped.

If the Control Bus card is already installed in the PC, the following dialog box may be
displayed.
030435E.ai
Fugure Found New Hardware
2. On the Found New Hardware dialog box, click [Ask me again later].
3. Set the ProSafe-RS installation CD-ROM. If the installer of .NET or ProSafe-RS is
automatically started, you need to terminate the installer.
4. Find the Setup.exe under \COMDRVOPN folder in the CD-ROM and run it.

5. In the User Account Control dialog box that appears, click [Continue].
030436E.ai
Figure User Account Control
030437E.ai
7. On the dialog box for confirming the installation that appears, click [OK] to continue.
8. Windows Security dialog box for installing [Yokogawa Network Adapters] will be displayed.
030438E.ai
Figure Windows Security (Yokogawa Network Adapters)

030439E.ai
Figure Installation Completed
TIP
If you have installed or deleted other devices anew before performing the new installation of the Open
Communication driver, a message requiring restarting of the PC may be displayed in the installation completion
message box. In this case, be sure to restart the PC after doing step 11.
11. Click [OK] and then remove the CD-ROM from the drive.


After installing the driver, in the Network Adapters folder of Device Manager should show
[Yokogawa Vnet/IP Open Communication Driver (BUS2)].
Device Manger can be started from Control Panel through Start menu.
If the adapter is not working properly, an exclamation mark (!) will be displayed next to the icon of
the network adapter.
030442E.ai

3.4.4 Installation of Open Communication Driver (Windows

XP/Windows Server 2003)
The procedure for installing the Open Communication driver in Windows XP or Windows
n Detailed Procedure of Installing Open Communication Driver
IMPORTANT
Before installing starts, the running programs such as anti-virus should be stopped.
1. Start Windows and log on as an administrative user.

If a VI702/VI701 card has been installed, a message box indicating Found New Hardware
appears, then the welcome dialog box of Found New Hardware Wizard appears.
If a VI702/VI701 card has not been installed, the message box and the wizard do not
appear.
Found New Hardware
Network Controller
Installing...
030410E.ai
Figure Found New Hardware Message Box
2. Click [Cancel] on Found New Hardware Wizard.

Found New Hardware Wizard
Welcome to the Found New

Hardware Wizard
This wizard helps you install a device driver for a
hardware device.
To continue, click Next.
<Back Next> Cancel
030411E.ai
Figure Found New Hardware Wizard
3. Load the CD-ROM of ProSafe-RS for installing to CD-ROM drive.

Terminate the installer of .NET or ProSafe-RS that is started automatically.
4. Execute Setup.exe in the COMDRVOPN folder in the installation CD-ROM.
Vnet/IP Open Communication Driver Setup
Welcome
This program let you install or uninstall Vnet/IP Open Communication Driver.
INSTALL
Install Vnet/IP Open Communication Driver to you system.
UNINSTALL
Remove installed Vnet/IP Open Communication Driver.
OK Cancle
030413E.ai
In the dialog box for confirming the installation, click [OK].

6. In the Hardware Installation dialog box that appears, click the [Continue Anyway] button.

Yokogawa Vnet/IP Open Communication Driver (BUS2)


030414E.ai
7. A message appears indicating that the installation is completed. Click [OK].
TIP
If you have newly installed or deleted other devices before the new installation of the Vnet/IP Open
Communication Driver, a message requiring restarting of the PC may be displayed in the installation completion
message box. In this case, be sure to restart the PC.
8. In the case of Windows XP, when a message indicates that a new network device installed
appears, click the close mark on the upper-right corner of the message to close it. Do not
start the network setup wizard. If you happen to start the wizard, click [Cancel] to stop it.

n Confirm the Added Driver

After installing the driver, [Vnet/IP Open Communication Driver(BUS2)] should display in Network
Adapters folder in [Device Manager] window.
Computer Management
Action View
Tree
HIS0124
Computer Management DVD/CD-ROM drives
System Tools IDE ATA/ATAPI controllers
Event Viewer SCSI and RAID controllers
System Information USB (Universal Serial Bus) controllers
Performance Logs and Alerts Keyboards
Shared Folders Computer
Device Manager Sound, video and game controllers
Local Users and Groups System Devices
Storage Other devices
Disk Management Disk drives
Disk Defragmenter Display adapters
Logical Drives Tape drives
Removable Storage Network adapters
Services and Applications Intel 8255x-based PCI Ethernet Adapter (10/100)
Vnet/IP Open Communication Driver(BUS2)
Floppy disk controllers
Floppy disk drives
Ports (COM & LPT)
Mice and other pointing devices
Monitors
030425E.ai
Figure When the Added Driver is Working Properly
If the driver is not working properly, an exclamation mark (!) is indicated for the network adapter.

3.4.5 Setting Vnet/IP Network Connection (Windows Vista/

In this section, how to set up the Vnet/IP network connection in a Windows Vista or
Windows Server 2008 PC will be explained.
n Procedure 1 Change Local Area Connection Name

The local area connection names automatically given by the system should be changed so that
the corresponding connections can be identified.
Change the local area connection names for Vnet/IP open communication and control bus
connection to VnetIPOpen and VnetIP, respectively. The procedure is the same as that for
Vnet connection.
SEE
ALSO For the procedure for renaming the local area connection, see the following:
n Procedure 1 Change Local Area Connection Names in 3.3.1, Setting Network Connection (Windows
Vista/Windows Server 2008)

standard setting of ProSafe-RS does not use DHCP, the IP addresses must be set explicitly. Set
the IP addresses respectively for both the open communication network and control bus network.
Note that this setting must be made even when the PC is used in a domain environment.
l Vnet/IP Open Communication IP Address

1. On the window of Network Connection, right click the icon of [VnetIPOpen], and choose
[Properties] from the menu so as to display the VnetIPOpen Properties window.
030446E.ai
Figure VnetIPOpen Properties

2. Set the check marks only for the following items in the area of [This connection uses the
following items].
Client for Microsoft Network
File and Printer Sharing for Microsoft Network
Link-Layer Topology Discovery Mapper I/O Driver
Link-Layer Topology Discovery Responder
IMPORTANT
The option of [Internet Connection Sharing] in [Sharing] tab of VnetIPOpen Properties window
should not be enabled.

4. Check [Use the following IP address] and set as follows. Vnet/IP Open Communication
address will be defined.
When using the existing setting
Enter the currently used IP address of the network environment.
When using the new setting in the new environment
IP address: 192.168.<128+Domain Number>.<129+Station Number> (*1)
Subnet mask: 255.255.255.0
Default gateway: No setting is required if no other Vnet/IP domain exists. When connecting
with other Vnet/IP domains, Layer3 switch IP address should be entered.
(Example) 192.168. <128+Domain Number>.253
030447E.ai
Figure Vnet/IP Open Communication IP Address (Example)
IMPORTANT
domain server.

1. On the window of Network Connection, right click the icon of VnetIP, and choose
[Properties] from the menu so as to display the [VnetIP Properties] window.
030448E.ai
Figure VnetIP Properties

030449E.ai
Figure Control Bus IP Address (Example)

When using the new setting in the new environment

*1: XXX.YYY stands for a subnet that is not identical with other subnet.

n Procedure 3 Bindings
Bindings for the Open Communication and Control Bus need to be defined. The Open
Communication should be placed at a higher priority than the Control Bus.
Bindings of the adapters can be defined on Advanced Settings window by clicking [Advanced]
on the Network Connections window.
030450E.ai
Figure Network Connections Window
1. Click [Advanced] on Network Connections window so as to call Advanced Settings

window.
TIP
If the menu of [Advanced] is not displayed, press Alt key will display the menu.
030451E.ai
Figure Before Changing Connection Order

For example, if the Control Bus is installed later than Open Communication, the Control Bus
will be at the higher position and connected first.
2. Click the upward or downward arrows next to Connections box so as to change the Open
Communication to the higher position than Control Bus.
030452E.ai
Figure After Changing Connection Order
As shown in the above example, when Open Communication is moved to the higher
position than VnetIP, click [OK].
After changing the connection order and bindings, there is no need to restart the PC.
IMPORTANT
Do not change the position of [Remote Access Connections] so as to keep it at the lowest
position.
Do not change the items in Provider Order tab.
Do not change the bindings for VnetIPOpen and VnetIP in the Bindings box below the
Connections box.

n Procedure 4 Change Computer Name

The computer name needs to be changed. The procedure is the same as described for V net.
SEE
ALSO For more information about changing computer name, see the following:
n Procedure 4 Change Computer Name in 3.3.1, Setting Network Connection (Windows Vista/Windows
Server 2008)
n Procedure 5 Set Network Location

The location type of the Undefined Networks need to be changed to [Private]. The procedure is
the same as described for V net.
SEE
ALSO For more information about changing the Network Location setting, see the following:
n Procedure 5 Set Network Location in 3.3.1, Setting Network Connection (Windows Vista/Windows
Server 2008)
n Procedure 6 Set Network and Sharing Center

The settings in Network and Sharing Center need to be changed. The procedure is the same as
described for V net.
SEE
ALSO For more information about changing the settings in Network and Sharing Center, see the following:
n Procedure 6 Set Network and Sharing Center in 3.3.1, Setting Network Connection (Windows Vista/

3.4.6 Setting Vnet/IP Network Connection (Windows XP/

In this section, how to set the Vnet/IP network connection in a PC of Windows XP or
Windows Server 2003 will be explained.
n Procedure 1 Rename Local Area Connection

The local area connection names automatically given by the system should be changed so that
the corresponding connections can be identified.
Change the local area connection names for Vnet/IP open communication and control bus
connection to VnetIPOpen and VnetIP, respectively. The procedure is the same as that for
Vnet connection.
SEE
ALSO For the procedure for renaming the local area connection, see the following:
n Procedure 1 Changing Local Area Connection Names in 3.3.2, Setting Network Connection (Windows
XP/Windows Server 2003)

standard setting of ProSafe-RS does not use DHCP, the IP addresses must be set explicitly. Set
the IP addresses respectively for both the open communication network and control bus network.
Note that this setting must be made even when the PC is used in a domain environment.
l Open Communication Network IP address

1. Open [VnetIPOpen] properties sheet in Network and Dial-up Connections.
VnetIPOpen Properties ?
General Sharing
Connect using:
Vnet/IP Open Communication Driver (BUS2)
Configure
Components checked are used by this connection:

Install Uninstall Properties
Description
Transmission Control Protocol/Internet Protocol.
The default wide area network protocol that provides communication
across deverse interconnected networks.
Show icon in taskbar when connected
OK Cancel
030420E.ai
Figure VnetIPOpen Properties

2. Choose Internet Protocol [TCP/IP] then click Properties button.
The window of Internet Protocol [TCP/IP] Properties displays.
3. Click Use the following IP address option, then set the IP address, Subnet mask and
Default gateway as follows.
If using a PC with previous environment settings, the existing network settings should be
entered.
If using a new PC, use the default settings according the station number.
The standard settings are as follows.
IP address: 192.168.<128+Domain Number>.<129+Station Number> (*1)
Subnet mask: 255.255.255.0
Default gateway: No setting is required if no other Vnet/IP domain exists. When connecting
with other Vnet/IP domains, Layer3 switch IP address should be entered.
(Example) 192.168. <128+Domain Number>.253
An example of the settings is shown as follows.

General
You can get IP settings assigned automatically if your network supports this capability.
Otherwise, you need to ask your network administrator for the appropriate IP settings.

IP address: 192 168 129 193
Subnet mask: 255 255 255 0
Default gateway: 192 168 129 253

Advanced...
OK Cancel
030421E.ai
Figure Open communication Network Address Settings
In the above figure, the IP address is set as 192.168.129.193.

The actual IP address should conform to the connected network.
Windows does not require restart after change the IP address settings.
IMPORTANT
domain server.

l Control Bus Network IP address
1. On Network and Dial-up Connections window, choose VnetIP then click Properties
button.
TIP
When settings on General tab of the properties sheet, the PC needs to be restarted.
3. Choose [Internet Protocol (TCP/IP)] and then click [Properties] so as to display the Internet
Protocol (TCP/IP) Properties window.
General
You can get IP settings assigned automatically if your network supports this capability.
Otherwise, you need to ask your network administrator for the appropriate IP settings.

IP address: 172 16 1 24
Default gateway:

Advanced...
OK Cancel
030422E.ai
Figure Control Bus Network Address Settings
4. Select the [Use the following IP address] option and set the IP address and subnet mask of
VnetIP to the default values that are determined according to the station address.
IMPORTANT
Do not set the default gateway.

Standard Setting:

n Procedure 3 Network Bindings

It is necessary to set the Open Communication Network with a higher priority than Control Bus
Network.
The bindings can be set on the Adapter and Bindings tab in Advanced Settings dialog.
1. On the window of Network and Dial-up Connections, in case of Windows XP, on Network
Connections window, choose [Advanced] - [Advanced Settings..].
The Advanced Settings dialog displays.
Advanced Settings ?
Connections are listed in the order in which they are accessed by DNS and
other network services.
Connections:
VnetIP
VnetIPOpen
Bindings for VnetIP:

OK Cancel
030423E.ai
Figure Before Bindings
In above figure, Control Bus Network adapter is installed later so that Control Bus Network
adapter has higher priority than Open Communication Network adapter.

2. In order to give Open Communication Network adapter a higher priority than Control Bus
Network, use the arrowhead buttons on the right side to move the adapter.
Advanced Settings ?
Connections are listed in the order in which they are accessed by DNS and
other network services.
Connections:
VnetIPOpen
VnetIP
Bindings for VnetIP:

OK Cancel
030424E.ai
Figure After Bindings
3. When Open Communication Network is set at higher position than Control Bus Network,
click [OK] to complete the bindings.
In Windows, there is no need to restart Windows after binding changes.
IMPORTANT
Leave the Remote Access Connections at the lowest position, do not change it.
There is no setting is required on Provider Order tab.
Do not change the bindings displayed in the Connections list box.

3.4.7 Reinstallation (for Vnet/IP)

The reinstallation procedures for the Control Bus driver and the ProSafe-RS system
software are described in this Section.
n Flow of Reinstallation
The media required for reinstallation are the same as those used for original installation.
SEE
ALSO For the required media, see the following:
n Item to be Prepared at Reinstallation of 5.2, Reinstallation of the ProSafe-RS Software
The following are the major steps of the reinstallation procedure:

1. Installation of Windows
This is not required when only the ProSafe-RS system needs to be reinstalled.
2. Updating the Windows network functions
Update the Windows network settings and reinstall (update) the control bus driver and Vnet/
IP Open Communication driver as necessary.
SEE
ALSO For how to update the control bus driver, see the following:
6.1, Procedure for Updating Control Bus Driver
For how to update the Vnet/IP open communication driver, see the following:
Update or Delete Vnet/IP Open Communication Driver (Windows Vista/Windows Server 2008)
Update or Delete Vnet/IP Open Communication Driver (Windows XP/Windows Server 2003)
For other network devices, reinstall and set up as instructed in the network card manual.
3. Reinstallation of the ProSafe-RS software
SEE
ALSO For the details of the reinstallation of the software, see the following:
5.2, Reinstallation of the ProSafe-RS Software

n Update or Delete Vnet/IP Open Communication Driver (Windows Vista/

l Procedure for Updating Vnet/IP Open Communication Driver

2. Set the CD-ROM for installing ProSafe-RS to drive.
If the ProSafe-RS installer is automatically started, you must terminate it.
3. Run Steup.exe in the \COMDRVOPN folder in the CD-ROM.
If the dialog box of User Account Control appears, click [Continue].
030440E.ai
Figure Install/Uninstall-Selection Dialog Box
TIP
If the latest version of Vnet/IP open communication driver is already installed, the install/uninstall-selection dialog
box appears with the [UNINSTALL] option selected and you cannot select [INSTALL]. In this case, click [Cancel]
to finish the task.
5. When a dialog box confirming the installation appears, click [OK].

6. Windows Security (Yokogawa Network Adapter) dialog box appears.
030454E.ai
Figure Windows Security [Yokogawa Network Adapter]

Click [Install] to continue.
Click [OK] and then remove the CD-ROM from the drive.
l Procedure for Deleting Vnet/IP Open Communication Driver

2. Set the ProSafe-RS CD-ROM to the drive.
If the ProSafe-RS installer is automatically started, you must terminate it.
3. Run Steup.exe in the COMDRVOPN folder in the CD-ROM.
In the User Account Control dialog box that appears, click [Continue].
4. In the install/uninstall-selection dialog box that appears, select [UNINSTALL] and click [OK].
TIP
If the Vnet/IP open communication driver is not installed, the install/uninstall-selection dialog box appears with the
[INSTALL] option selected and you cannot select [UNINSTALL]. In this case, click [Cancel] to finish the task.
5. When the dialog box confirming the uninstallation appears, click [OK].
6. A message appears indicating that the uninstallation is complete.
Click [OK] and then remove the CD-ROM from the drive.

n Update or Delete Vnet/IP Open Communication Driver (Windows XP/

How to update or delete Vnet/IP Open Communication driver in Windows XP or Windows Server
2003 environment will explained in this section.
l Updating Procedure
2. Insert the CD-ROM for updating the driver to CD-ROM drive.
Terminate the installer of ProSafe-RS that is started automatically.
3. Run Setup.exe command in the COMDRVOPN in the CD-ROM.
TIP
If the latest version of Vnet/IP open communication driver is already installed, the install/uninstall-selection dialog
box appears with the [UNINSTALL] option selected and you cannot select [INSTALL]. In this case, click [Cancel]
to finish the task.

6. The Hardware Installation dialog box appears. Click [Continue] to continue.
7. When a message appears indicating that the installation is complete, click [OK] to finish the
task.
l Deleting Procedure
2. Insert the CD-ROM for the driver to CD-ROM drive.
Terminate the installer of ProSafe-RS that is started automatically.
3. Run Setup.exe command in the COMDRVOPN folder in the CD-ROM.
TIP
If the Vnet/IP open communication driver is not installed, the install/uninstall-selection dialog box appears with the
[INSTALL] option selected and you cannot select [UNINSTALL]. In this case, click [Cancel] to finish the task.
5. When a dialog box confirming the uninstallation appears, click [OK].

6. When a message appears indicating that the uninstallation is complete, click [OK] to finish
the task.

Blank Page
<4.1 New Installation of Software> 4-1
4. New Installation of ProSafe-RS

Software
This chapter explains preparation for a new installation of the ProSafe-RS software on a
general-purpose PC, the installation procedure and items to be set after the installation.
4.1 New Installation of Software

This section explains preparation to be made before installing the ProSafe-RS software
and the procedure of new installation.
n About Administrative User

The installation of ProSafe-RS should be performed by an administrative user.
In Windows XP/Windows Server 2003/Windows Server 2008, the user of Administrator account
is an administrative user.
However, in Windows Vista, user cannot logon by the account of Administrator. The
administrative user in Windows Vista is the user who is created at the installation of the Windows
Vista OS.
During installation of ProSafe-RS, if the standard model of security settings is applied by Security
Setting Utility, the ProSafe-RS related folders will be restricted for access. The user without the
access privilege cannot access the installation folders.
Once the standard model of security setting has been applied, the installation next time must
be executed by an administrative user who belongs to the user group for maintenance (PSF_
MAINTENANCE).
The administrative user who executes the Security Setting Utility will be automatically added to
the PSF_MAINTENANCE user group when the user applies the [Stand alone: Set the security
for local account (standard model)] of security settings.
n Cautionary Notes on Installation

When installing the ProSafe-RS software, the following items need to be noticed.
When ProSafe-RS is used in Windows domain environment and applied with the standard
model of PC hardening, make sure that the following settings are already performed
beforehand.
- The administrative user for installing ProSafe-RS is already created in the domain
controller.
- The user groups of ProSafe-RS are already created in the domain controller.
- The user who performs the installation should be added to the Domain Admins user
group and PSF_MAINTENANCE user group.
The messages in the dialog boxes of the installer are displayed in Japanese if the operating
system is Japanese; otherwise, the messages are displayed in English. The language in the
dialog box is irrelevant to the language of the keycode FD.
When installing ProSafe-RS package to the PC of Windows Vista, right after the installer
starts, a User Account Control dialog box may be displayed for confirmation. In this case,
click [Continue] to continue the installation.

n Behavior of Installer
When installing ProSafe-RS packages, the installation related dialog boxes may be hidden by
other windows. In this case, you need to pay attention to the Windows taskbar during installation.
When installing the ProSafe-RS packages, the installation progress bar for the Workbench
installation may be hidden by the installer window. If you want to check the installation
progress, you need to click the Workbench setup program button on the Windows taskbar.
When an error occurs during installation, the error dialog box may be hidden by the installer
window and it looks that the installation is freezing. In this case, you need to click the error
dialog box button on the Windows taskbar so as to display the error dialog box at the front
and follow the error dialog messages.
n Window Displayed During Installation

When installing ProSafe-RS packages, a window may be displayed indicating that the files you
are trying to install are being used.
YOKOGAWA ProSafe-RS Setup
Files in Use
Some files that need to be updated are currently in use.
The following applications are using files that need to be updated by this setup.
BK Bossd
BK SIMMGR
Automatically close and attempt to restart applications.

Do not close applications. (A reboot will be required.)
InstallShield
OK Cancel
040105E.ai
Figure Window Informing that the Files are being Used
Since there is no problem in the installation, select [Do not close applications. (A reboot will be
required.) ] and click the [OK] button to continue the installation.
A warning message box having only the [OK] and [Cancel] buttons might be displayed instead of
the above described window. In this case, click [OK] to continue the installation.

n Items to be Prepared at New Installation

Prepare the following items so that they are at hand before a new installation of the software.
ProSafe-RS software CD-ROM (CHSKM02)
ProSafe-RS keycode FD (CHSCM01) (In some cases, multiple FDs are provided.)
ProSafe-RS Project ID license (CHSPJT)
n Preparation before New Installation

Carry out the following tasks before starting the installer.
1. Stop the operation of resident programs, including anti-virus software, if they are running,
before installation.
2. Restart the PC immediately before installation. This operation is not required if the PC has
already been restarted in the process of installation tasks.
TIP
Restart the PC after installing the ProSafe-RS software.
n Procedure of New Installation
IMPORTANT
Be sure to install Microsoft .NET Framework 3.5 SP1 if it has not been installed on the PC. When
the installation is started, the setup program of Microsoft .NET Framework 3.5 SP1 starts up
automatically.
1. Log on as a user with the Administrative privilege who has a role for the ProSafe-RS
software installation. If your PC is a member of a Windows domain, log on to the PC using a
domain user account.
2. Close all applications.
3. Insert the keycode FD into the FD drive.
4. Insert the ProSafe-RS CD-ROM into the CD-ROM drive.
The Setup program automatically starts up. If it does not automatically start up, double-click
(CD-ROM drive name:) \setup.exe from Windows Explorer.

5. The following dialog box appears if Microsoft .NET Framework 3.5 SP1 and Microsoft Visual
C++ 2008 Redistributable have not been installed.
Install them by following the guidance. If you are required to restart the PC, then restart it.
040101E.ai
Figure Setup Requirements Dialog Box
6. The installation of .NET Framework and Microsoft Visual C++ 2008 Redistributable finishes.
After the Welcome dialog box appears, a dialog box asking whether there is a second
keycode FD appears.
Insert next Keycode floppy disk and click Yes.

If next Keycode floppy disk does not exist, click No.
Yes No
040103E.ai
Figure Keycode FD Replacement Confirmation Dialog Box
7. Click the [No] button if there is only one keycode FD.

If there are several keycode FDs, replace the keycode FD and click the [Yes] button. Click
the [No] button after inserting the last key code FD.
8. Click the [Next] button in the Welcome dialog box. The Customer Information dialog box
appears.
9. Enter the user name and department in the Customer Information dialog box and click the
[Next] button. The ID Number dialog box appears.

10. Enter the ID number (in a 8-digit number) written in the Project ID license in the ID Number
dialog box and click the [Next] button.
The Package List dialog box appears.
Package List
Packages will be installed is as follows:
CFS1100 Safety Control Function

CHS2100 SOE Viewer Package
CHS2200 SOE OPC interface Package
CHS5100 Safety System Generation & Maintenance Package
CHS5200 CENTUM VP/CS3000 Intergration Engineering Package
CHS5400 Electronic Instruction Manual
Install to:
C:\Program Files\ProSafe-RS\ change...
InstallShield
Space < Back Next > Cancel
040104E.ai
Figure Package List Dialog Box
11. The Package List dialog box displays a list of packages that will be installed from now.
There is no need to change the settings in the dialog box. It is recommended to use the
default installation destination. Click the [Space] button to check the disk space of the
installation destination.
Click the [Next] button. The Ready to Install the Program dialog box appears.
12. Click the [Install] button in the Ready to Install the Program dialog box to start the
installation.
The progress is displayed during the installation.
13. When copying file is completed, Security Setting Utility will be started. The security settings
can be defined according to the system information security policy.
SEE
ALSO For more information about setting information security, see the following:
11, Security Setting Utility
14. If you have completed the settings of PC hardening, the installation complete dialog box will
appear.
A dialog box prompting to restart the PC appears.
15. Remove the keycode FD and the CD-ROM from each drive and click the [Yes] button in the
dialog box to restart the PC. Click the [No] button to restart the PC later.
IMPORTANT
Installed packages do not operate properly until the PC is restarted after installing the ProSafe-
RS software.

<4.2 User Account and Folder Settings> 4-6
4.2 User Account and Folder Settings

The Prosafe-RS user accounts should be created and defined on ProSafe-RS for each
user.
When standard model of PC hardening is selected, a set of security settings will be
applied to the installation folders and registries according to the access privileges of
ProSafe-RS user groups by Security Setting Utility. Therefore, when the user accounts are
created, the created users need to be registered to the ProSafe-RS user groups.
In this section, how to create user accounts in the PC that belongs to a workgroup and
how to register users to user groups will be explained.
4.2.1 Create User Accounts on Workgroup Member PC

Regardless of the model of information security settings is selected for the PC, as long
as the PC is a member of a Windows workgroup, the needed user accounts should be
created on the PC. If the standard model of information security settings is selected
for the PC, the user accounts according to various user privileges should be created
accordingly.
SEE
ALSO For more information about the user accounts for various privileges, see the following:
The procedure for creating user accounts is as follows:
n Procedure for Creating User Accounts

1. Logon to an administrative user account.
2. In Windows Vista/Windows Server 2008, right click [Computer], otherwise, right click
[My Computer], and then choose [Manage] from the context menu so as to display the
Computer Management window (in Windows Server 2008, Server Manager is displayed).
3. From the tree-view in the left pane, choose Local Users and Groups and then select the
Users folder under it (In Windows Server 2008, Local Users and Groups is found under
Configuration).
4. Choose [New Users] from [Action] menu so as to display the New User dialog box.
5. Enter the user name and password respectively.
6. If necessary, the option [User must change password at next logon] may be unchecked
and the option [Password never expires] may be checked. The creation of a user account is
completed.
7. Logon to the newly created user account to make sure the account is properly added.

4.2.2 When Choosing Standard Model of Information

Security
When choosing standard model of information security settings, the user accounts need
to be added to the user groups. How to add the user accounts to the user groups will be
explained in this section. The notices and settings after choosing the standard model of
security will also be explained.
SEE
ALSO For more information about preparations before adding users to a user group, see the following:
Settings for the Windows Workgroup Member PC

The user accounts for engineers and maintenance personnel should be registered to the user
groups according to their privileges.
Procedure of Adding User Account to User Group

1. Open [Computer Management], choose a user account and open [Member Of] tab.
2. Click [Add] and then add this account to a proper ProSafe-RS group according to the user
privilege.
3. Close Computer Management.
IMPORTANT
The user who is registered to the PSF_MAINTENANCE user group must be registered to
Administrators user group.
Settings for the Windows Domain Member PC

1. The domain user accounts for engineers and maintenance personnel should be registered
to the user groups on Windows domain controller according to their privileges.
SEE
ALSO For more information about adding user to user group on Windows domain controller, see the following:
2. On the Windows domain controller, the further settings in the following is needed:
IMPORTANT
The users that belong to PSF_MAINTENANCE group must be registered to the Domain Admins
group.

3. On the client PCs belong to the Windows domain, the settings with following procedure are
required:
IMPORTANT
The users that belong to PSF_MAINTENANCE_LCL group must be registered to the
Administrators group of the local PC.
The administrative users of the local PC must be registered to the PSF_MAINTENANCE_
LCL group.
n Settings for Integration with CENTUM VP

The settings required for the system integrated with CENTUM VP with the Standard model
security setting will be explained in this section.
IMPORTANT
When integrating a system with CENTUM VP with the Standard model security setting, the
descriptions in this section must be followed.
l Required Settings when Referencing CENTUM VP Project

When performing the engineering work of CENTUM VP integration, the user that uses SCS
Manager needs to be registered to the following user groups.
ProSafe-RS User Group: PSF_ENGINEER
CENTUM VP User Group: CTM_ENGINEER
l When using CENTUM VP SOE Viewer

When using CENTUM VP SOE Viewer to display the SOE data of SCS, the user that uses the
CENTUM VP SOE Viewer needs to be registered to the PSF_OPERATOR user group.
l When Referencing CENTUM VP HIS Log on ProSafe-RS SOE Viewer

When referencing CENTUM VP HIS log on ProSafe-RS SOE Viewer, the user that uses the
ProSafe-RS SOE Viewer needs to be registered to the CTM_OPERATOR user group of
CENTUM VP.

l When using SCS Simulator
When using SCS Simulator, the users of the SCS Manager and System View needs to be
registered to the following user groups:
ProSafe-RS User Group: PSF_ENGINEER
CENTUM VP User Group: CTM_ENGINEER
When performing expanded test functions during SCS Simulation Test, the user of CTM_
PROCESS in the PC installed with ProSafe-RS package, CENTUM VP Test Function package,
Expanded Test Function package, HIS Simulator package and FCS Simulator package should
be added to the ProSafe-RS user groups accordingly under the following circumstances:
CENTUM VP and ProSafe-RS are running in Windows domain environment
Add the CTM_PROCESS user to PSF_OPC_LCL group.
CENTUM VP and ProSafe-RS running in Windows workgroup environment
Add the CTM_PROCESS user to PSF_OPC group.
n Settings for SOE OPC Interface

Standard model of security settings restricts the access to DCOM. With this restriction, only the
users belong to ProSafe-RS user groups can access the SOE OPC interface. Therefore, the
following settings need to be performed on the OPC server, the PC installed with SOE OPC
Interface package (CHS2200).
l When the PC is a Member of Workgroup

1. Create a User Account
A user of OPC client needs to be created on SOE OPC server. The combination of the user
name and password should be the same in server PC and in client PC.
2. Register the User in User Group of PSF_OPC
The user created in step 1 needs to be registered in PSF_OPC user group.
For example, for accessing SOE OPC interface from Exaquantum, a quantumuser user
account is created on the SOE OPC server, and this user account should be registered to
PSF_OPC user group
l When the PC is a Member of Windows Domain

Setup For a Local User Account
A local user account of OPC client needs to be created on SOE OPC server. The
combination of the user name and password should be the same in server PC and in
client PC.
2. Register the User in User Group of PSF_OPC
The user created in step 1 needs to be registered in PSF_OPC_LCL user group.
Setup For a Domain User Account
A domain user account of OPC client needs to be registered in PSF_OPC user group.

n Settings for the Case When SOE OPC Interface Package and CENTUM
VP Exaopc OPC Interface Package are Installed in the Same PC
If you installed the SOE OPC Interface Package (CHS2200) for ProSafe-RS R2.01.00 and later
versions and Exaopc OPC Interface Package (for HIS) (LHS2411) for CENTUM VP R4.01.00
and later versions in the same PC and selected the Standard Model security settings for
information security, you need to make the following settings.
l When the PC is a Member of Workgroup

Settings on the OPC server PC:
1. Add the CTM_PROCESS user to the PSF_OPC user group.
2. Add the EXAUSER user to the CTM_OPC user group.
3. Create user accounts that have the same user names as those of the OPC client users and
add them to the CTM_OPC and PSF_OPC user groups.
4. After completing the above settings, restart the OPC server PC.
Settings on an OPC client PC:

1. Add the users of the OPC client to the CTM_OPC user group (for use with CENTUM VP).
2. Add the users of the OPC client to the PSF_OPC user group (for use with ProSafe-RS).
3. After completing the above settings, restart the client PC.
l When the PC is a Member of Windows Domain

For use as a domain user:
Set as follows on the domain controller PC.
1. Add the users of the OPC client to the CTM_OPC , PSF_OPC user group.
Set as follows on the OPC server PC.

1. Add the CTM_PROCESS user to the PSF_OPC_LCL user group.
2. Add the EXAUSER user to the CTM_OPC_LCL user group.
For use as a local PC user:

Set as follows on the OPC server PC.
1. Add the CTM_PROCESS user to the PSF_OPC_LCL user group.
2. Add the EXAUSER user to the CTM_OPC_LCL user group.
3. Create user accounts that have the same user names as those of the OPC client users
and add them to the CTM_OPC_LCL and PSF_OPC_LCL user groups.
Set as follows on an OPC client PC.

1. Add the users of the OPC client to the CTM_OPC user group (for use with CENTUM
VP).
2. Add the users of the OPC client to the PSF_OPC user group (for use with ProSafe-
RS).
3. After completing the above settings, restart the client PC.

n Setup for Message Cache Tool

For caching the messages corrected by other stations in Message Cache Tool, the following
setups are required.
l On Workgroup Member PC
A user account needs to be created on the station from which the data are acquired. The
user account name and password should be the same as the user account in the PC that
the Message Cache Tool is installed.
2. Register the User to PSF_ENGINEER Group
The created user account should be registered to PSF_ENGINEER user group.
l On Windows Domain Member PC

Register the user for using the Message Cache Tool to PSF_ENGINEER user group.
n Security Setting for Project Data Folders

When standard model of PC hardening is selected, the following access permissions will be
automatically applied to the project data folder (C:\RS-Projects as default setting). If the project
data are stored in a different folder, the security settings for the folder need to be manually
applied by referencing the default setting described below.
Table Security Setting for Project Data Folder
Windows Environment
Windows Domain Workgroup
User Group
PSF_OPERATOR Full Access Control Full Access Control
PSF_ENGINEER Full Access Control Full Access Control
PSF_MAINTENANCE Full Access Control Full Access Control
PSF_MAINTENANCE_LCL Full Access Control N/A
PSF_OPC Full Access Control Full Access Control
PSF_OPC_LCL Full Access Control N/A
PSF_UTL Read Read
Local System Full Access Control Full Access Control

<4.3 Settings after Software Installation> 4-12
4.3 Settings after Software Installation

This section explains settings required after installing the ProSafe-RS software. It also
explains settings required when connecting an uninterruptible power source (hereinafter
referred to as UPS) to a general-purpose PC.
n Display Properties (Windows Vista/Windows Server 2008)

The display properties should be defined for each user that operates the ProSafe-RS software.
Each user needs to logon to the PC and define the display properties.
l Desktop Background
1. Logon to the PC using a user account that uses ProSafe-RS software.
2. Call Control Panel from the Start menu and select [Personalization]-[Desktop background].
040306E.ai
Figure Desktop Background
3. Choose [Solid Colors] for [Desktop Background].
TIP
When the background color is defined as a solid color and select a color at the first logon, the background color
may revert to black at the second logon. When this problem occurs, you need to define the background color
again.

l Screen Saver
1. Call Control Panel from Start menu, and select [Personalization] - [Screen Saver Settings].
040307E.ai
Figure Screen Saver
2. Choose [None] for [Screen saver].

l Display Settings
1. Call Control Panel from Start menu, and select [Personalization] - [Display Settings].
040308E.ai
Figure Display Settings
2. Choose [Highest (32 bit) ] for [Colors].

n Display Property Setting (Windows XP/Windows Server 2003)

The following shows how to set display properties.
2. Select [Control Panel] and [Display] from the [Start] menu to open the [Display Properties]
dialog box.
3. Make settings in the following tabs.
l [Desktop] Tab
Set [Background] to [None].
Display Properties
Themes Desktop Screen Saver Appearance Settings
Background:
(None) Browse...
Ascent
Position:
Autumn
Stretch
Azul
Bliss Color:
Blue Lace 16
Customize Desktop...
OK Cancel Apply
040309E.ai
Figure [Desktop] Tab

l [Screen Saver] Tab
Set [Screen saver] to [None].
Display Properties
Screen saver
(None) Settings Preview
Wait: 10 minutes On resume, password protect
Monitor power
To adjust monitor power settings and save energy,
click Power
Power...
OK Cancel Apply
040310E.ai
Figure [Screen Saver] Tab

l [Settings] Tab
It is recommended to set the display properties as follows.
Screen resolution: 1280 by 1024 pixels
Color quality: Medium (16 bit)
Display Properties
Drag the monitor icons to match the physical arrangement of your monitors.
Display:
1. SONY CPD-17SF8R on ATI FireGL V3100
Screen resolution Color quality

Less More Medium (16 bit)
1280 by 1024 pixels
Use this device as the primary monitor.

Extend my Windows desktop onto this monitor.
Identify Troubleshoot... Advanced
OK Cancel Apply
040311E.ai
Figure [Settings] Tab
TIP
Specify 256 colors only if the VRAM is insufficient.

n Printer Setup
If a printer is used, refer to the printers manual and make necessary settings.
n Recommended UPS Software

It is possible to install UPS software and make various settings in order to protect data in the
general-purpose PC at power supply failures, etc.
The following UPS software is recommended.
Windows standard UPS software
POWERCHUTE Business Edition
Specify the UPS battery operation time such that the PC can continue operating with the UPS
battery without shutting it down if a power supply error (e.g. power interruption) occurs for a short
period of time. Use several seconds as a guideline for setting the UPS battery operation time.
TIP
The UPS battery operation time can be set longer than several seconds, but the PC should be shut down if a
power interruption of more than a few seconds occurs for safety reasons.

n Setting Example when Using Windows Standard UPS Software

An example procedure for UPS settings using the Windows XP and Windows Server 2003
standard function is shown below.
TIP
When connecting UPS through serial cable (RS-232C) to the Windows Vista PC, the recommended UPS
software should be used.
The standard UPS features in Windows Vista are supported for the UPS connected through USB port only.
For more details about the setups of UPS, see the instruction manuals attached to the UPS and the Windows
Vista Help items.
l Displaying the Windows Standard UPS Setting Dialog Box

Click [Power Options] in Control Panel.
The following dialog box appears.
Power Options Properties ?
Uninterruptible Power Supply

Status
Current power source:
Estimated UPS runtime:
Estimated UPS capacity:
Battery condition:
Details
Manufacturer: [None]
Model:
Configure... Select...
The UPS service is currently stopped.
About...
OK Cancel Apply
040301E.ai
Figure Windows Standard UPS Setting Dialog Box

2. Click the [Select] button in the [UPS] tab of the Power Option Properties window.
UPS Selection ?
Select manufacturer: On port:

American Power Conversion COM3:
Select model:
Back-UPS
Back-UPS Pro
Basic Port on Communications Accessory
Basic signaling to any APC UPS
Matrix-UPS
PowerStack
Smart signaling to any APC UPS
Smart-UPS
Symmetra Power Array
Finish Cancel
040302E.ai
Figure UPS Selection Dialog Box
3. Select the UPS manufacturer, model and port to which the UPS is connected.
4. After the specification, click the [Finish] button.
5. Click the [Configure] button in the [UPS] tab of the Power Option Properties dialog box.
UPS Configuration ?
Enable all notifications.

Seconds between power failure and first notification: 5
Seconds between subsequent power failure notifications: 120
Critical alarm
A critical alarm occurs when the UPS battery is almost exhausted or,
optionally, after a specified time on battery power.
Minutes on battery before critical alarm: 2
When the alarm occurs, run this program:

BKHAcFailShut.exe Configure...
Next, instruct the computer to:

Shutdown
Finally, turn off the UPS.
OK Cancel
040303E.ai
Figure UPS Configuration Dialog Box
6. Enter each setting in accordance with the specifications of the connected UPS.
7. Click the [OK] button.
8. Return to the Power Option Properties dialog box and click the [OK] button or the [Apply]
button.
The settings are saved.

l Starting UPS Service
1. Start the UPS service by selecting [Administrative Tools] and then [Services] in [Control
Panel].
Services
Action View
Name Description Status Startup Type Log On As
Tree
Remote Procedure Call (RPC) Lo... Manages the... Manual LocalSystem
Services (Local)
Remote Registry Service Allows rem... Started Automatic LocalSystem
Removable Storage Manages r... Started Automatic LocalSystem
Routing and Remote Access Offers rout... Disabled LocalSystem
RunAs Service Enables st... Started Automatic LocalSystem
Security Accounts Manager Stores sec... Started Automatic LocalSystem
Server Provides R... Started Automatic LocalSystem
Smart Card Manages a... Manual LocalSystem
Smart Card Helper Provides s... Manual LocalSystem
System Event Notification Tracks syst... Started Automatic LocalSystem
Task Scheduler Enables a... Started Automatic LocalSystem
TCP/IP NetBIOS Helper Service Enables su... Started Automatic LocalSystem
Telephony Provides T... Started Manual LocalSystem
Telnet Allows are... Manual LocalSystem
Uninterruptible Power Supply Manages a... Started Manual LocalSystem
Utility Manager Starts and... Manual LocalSystem
Windows Installer Installs, re... Manual LocalSystem
Windows Management Instrumen... Provides sy... Started Automatic LocalSystem
Windows Management Instrumen... Provides sy... Started Manual LocalSystem
Windows Time Sets up......... Started Automatic LocalSystem
040304E.ai
Figure Services Window
2. Select [Uninterruptible Power Supply] and display the Properties dialog box.
Uninterruptible Power Supply Properties (Local Computer) ?
General Log On Recovery Dependencies
Service name: UPS
Display name: Uninterruptible Power Supply
Description: Manages an uninterruptible power supply (UPS) connec...
Path to executable:
C:\WINNT\System32\ups.exe
Startup type: Auto
Service status: Stopped
Start Stop Pause Resume
You can specify the start parameters that apply when you start the service
from here.
Start parameters:
OK Cancel Apply
040305E.ai
Figure Uninterruptible Power Supply Properties
3. Set [Startup type] to [Automatic].

4. Click the [Start] button.
The service is started.

<4.4 Online Manual Setting> 4-22
4.4 Online Manual Setting

The online manual package is installed at the same time as the ProSafe-RS software. This
section explains about installation of the software for viewing the online manual.
n Installing the Document Viewer for the Online Manual

To browse the online manual in optimal condition, use it in the recommended environment.
The online manual is assumed to run in an environment where the following application is
installed.
Adobe Reader 9.2.0(*1)
*1: If you install the ProSafe-RS online manuals in a PC installed with the electronic documents of CS 3000, use the Adobe Reader
that is already installed for browsing CS 3000 documents.
If you install the ProSafe-RS online manuals in a PC installed with the electronic documents of CENTUM VP, you need to get
Adobe Reader and install it.
l Installation of Adobe Reader

Adobe Reader is not included in the product CD-ROM. You need to get it separately and install it.
l Settings After Installing Adobe Reader 9.2.0

When Adobe Reader 9.2.0 is used, make sure that the option [Open cross-document links in
same window] is checked.
The option [Open cross-document links in same window] can be redefined by choosing
[Preferences] [Documents] from the [Edit] menu of Adobe Reader 9.2.0. It is necessary to do
this setting in each logon user.

<5. Addition of ProSafe-RS Software Packages (without Revision Upgrade) and ...> 5-1
5. Addition of ProSafe-RS Software

Packages (without Revision
Upgrade) and Reinstallation
This chapter explains the procedure for adding packages without upgrading the revision
of the ProSafe-RS software and the procedure for reinstalling the software on a PC on
which the ProSafe-RS software has already been installed.
n Notes on Installation
When installing ProSafe-RS packages in Windows Vista/Windows Server 2008
environment, after starting the installer, a dialog box of User Account Control may be
displayed. You need to click [Continue] on this dialog box.
During installation, the installation related dialog boxes, such as those showing the
installation progress bar and error message, may be hidden behind the installer window.
If this happens, click the corresponding button on the Windows taskbar to show the dialog
box.
When you install the ProSafe-RS packages, a window may be displayed indicating that the
files you are trying to install are being used. Since there is no problem in the installation.
choose [Do not close applications. (A reboot will be required.) ] and click [OK] to continue
the installation. If the window has only the [OK] and [Cancel] buttons, just click [OK] to
continue the installation.

<5.1 Addition of ProSafe-RS Software Packages (without Revision Upgrade)> 5-2
5.1 Addition of ProSafe-RS Software Packages

(without Revision Upgrade)
This section explains the procedure for adding packages without upgrading the revision
of the ProSafe-RS software.
SEE
ALSO For the procedure to upgrade the revision when adding packages, see the following:
6.3, Revision Upgrade of ProSafe-RS Software (with Package Addition)
n Items to be Prepared at Adding Packages (without Revision Upgrade)

Prepare the following items so that they are at hand before adding packages without upgrading
the revision.
ProSafe-RS keycode FD for additional packages (CHSCM01)
ProSafe-RS software CD-ROM (CHSKM02): Containing the revision installed on the PC
IMPORTANT
In the package addition procedure (without revision upgrade), only packages whose codes are
stored in the keycode FD are installed. Packages that have already been installed on the PC can
be installed again if their keycodes are included in the keycode FD.
n Preparation before Adding Packages (without Revision Upgrade)

Perform the following tasks before starting the installer.
Stop the operation of resident programs, including anti-virus software, if they are running,
Restart the PC immediately before installation.

n Package Addition Procedure (without Revision Upgrade)

1. Log on to the PC as the administrative user who installed the ProSafe-RS package at the
first time.
IMPORTANT
Be sure to insert the keycode FD in the FD drive first and then insert the ProSafe-RS software
CD-ROM in the CD-ROM drive. If the keycode FD is not inserted first, a warning dialog box
appears during the installation and the installation is aborted.

3. Insert the keycode FD containing codes for additional packages into the FD drive.
The Setup program automatically starts up. If it does not start up automatically, double-click
setup.exe in the CD-ROM via Windows Explorer.
The Welcome dialog box appears.
5. Click the [Next] button in the Welcome dialog box. The Program Maintenance dialog box
appears.
Program Maintenance
Modify, or repair the program.
Modify
Add the packages. It is necessary to set Keycode FD before the setup
is stared.
Repair
Reinstall the packages. This option can restore deleted file and registry.
Keycode FD is not used.
InstallShield
050101E.ai
Figure Program Maintenance Dialog Box

6. Select the [Modify] radio button in the Program Maintenance dialog box and click the
[Next] button.
Package List
CHS5200 CENTUM VP/CS 3000 Integration Engineering Package

InstallShield
050102E.ai
Figure Package List Dialog Box (Initial Display)
7. In the default display of the Package List dialog box, a cross (X) symbol is placed on the
icons to the left of the names of the packages to be additionally installed (indicating the
status where installation is disabled). Change all the icons to display hard disk symbols
(status where installation is enabled).
Package List
CHS5200 CENTUM VP/CS 3000 Integration Engineering Package

InstallShield
050103E.ai
Figure Package List Dialog Box (After Selecting the Icons)
IMPORTANT
Be sure to change all the icons of displayed packages to the status where installation can be
performed.

8. Click the [Next] button in the Package List dialog box.
A dialog box confirming the changes to the icons appears.
Please confirm the icon of all packages was changed fr...

to
InstallShield
Yes No
050104E.ai
Figure Confirm Dialog Box
9. If the icons of all packages are changed correctly, click the [Yes] button in the dialog box
confirming icon changes.
The Ready to Install the Program dialog box appears.
If the package icons have not been changed correctly, click the [No] button in the dialog box
confirming icon changes and change the icons in the Package List dialog box to the status
where installation is allowed.
installation.
During the installation, the installation progress is displayed in the dialog box.
The installation completion message appears when the installation is finished.
11. Click the [Finish] button in the installation completion message box.
IMPORTANT
RS software.
n Tasks after Revision Upgrade (with Package Addition)

After the installation tasks are completed, it is possible to use Software Configuration Viewer
to put several keycode FDs together in one FD. By performing this task, it becomes possible to
install all the packages with a single keycode FD from the next installation.

<5.2 Reinstallation of the ProSafe-RS Software> 5-6
5.2 Reinstallation of the ProSafe-RS Software

This section explains the procedure to reinstall the software on a PC on which the
ProSafe-RS software has already been installed. It may for instance be necessary to
reinstall the software if you accidentally deleted part of the ProSafe-RS software or in
other similar situations.
SEE
ALSO If the software does not run properly even if the reinstallation procedure explained in this section is performed,
uninstall the ProSafe-RS software and then upgrade the revision (without adding packages).
For the procedure to uninstall the ProSafe-RS software, see the following:
Uninstalling ProSafe-RS Software in 7.3, ProSafe-RS Software Installation Troubleshooting
For the procedure to upgrade the revision (without adding packages), see the following:
6.2, Revision Upgrade of ProSafe-RS Software (without Package Addition)
n Item to be Prepared at Reinstallation

Prepare the following item so that it is at hand before performing reinstallation.
ProSafe-RS Software CD-ROM (CHSKM02): Containing the revision installed in the PC.
n Preparation before Reinstallation

Restart the PC immediately before installation.

<5.2 Reinstallation of the ProSafe-RS Software> 5-7
n Reinstallation Procedure
IMPORTANT
Do not use the keycode FD at reinstallation.
1. Use the same administrative user account that installed the ProSafe-RS at the first time to
logon the PC.
The Welcome dialog box appears.
4. Click the [Next] button in the Welcome dialog box. The Program Maintenance dialog box
appears.
Program Maintenance
Modify, or repair the program.
Modify
Add the packages. It is necessary to set Keycode FD before the setup
is stared.
Repair
Reinstall the packages. This option can restore deleted file and registry.
Keycode FD is not used.
InstallShield
050201E.ai
Figure Program Maintenance Dialog Box
5. Select the [Repair] radio button in the Program Maintenance dialog box and click the
[Next] button.
installation.
8. Remove the CD-ROM from the CD-ROM drive and click the [Yes] button in the dialog box to
restart the PC. Click the [No] button to restart the PC later.
IMPORTANT
RS software.

Blank Page
<6. Revision Upgrade of ProSafe-RS Software> 6-1
6. Revision Upgrade of ProSafe-RS

Software
This chapter explains the procedure for upgrading the ProSafe-RS software revision.
When upgrading the revision, it may become necessary to update the control bus driver.
Thus the procedure to update the control bus driver is also explained here. Refer to the
explanation as necessary.
The procedure for upgrading the revision of the ProSafe-RS software is explained for two
cases: when packages are not added and when they are added. Refer to the appropriate
section.
n Notes on Installation
When installing ProSafe-RS packages in Windows Vista/Windows Server 2008
environment, after starting the installer, a dialog box of User Account Control may be
displayed. You need to click [Continue] on this dialog box.
During installation, the installation related dialog boxes, such as those showing the
installation progress bar and error message, may be hidden behind the installer window.
If this happens, click the corresponding button on the Windows taskbar to show the dialog
box.
When you install the ProSafe-RS packages, a window may be displayed indicating that the
files you are trying to install are being used. Since there is no problem in the installation.
choose [Do not close applications. (A reboot will be required.) ] and click [OK] to continue
the installation. If the window has only the [OK] and [Cancel] buttons, just click [OK] to
continue the installation.
SEE
ALSO For the procedure to update the control bus driver, see the following:
6.1, Procedure for Updating Control Bus Driver
For the explanation about upgrading the revision without adding ProSafe-RS software packages, see the
following:
For the explanation about upgrading the revision with addition of ProSafe-RS software packages, see the
following:
For more information about version upgrade installation of ProSafe-RS software packages, see the
following:
6.4, ProSafe-RS Software Version Upgrade

<6. Revision Upgrade of ProSafe-RS Software> 6-2
n Flow of Revision Upgrade

The flowchart below shows the flow of upgrading the revision of the ProSafe-RS software.
Start
Does the control N

bus driver require
updating?
Update the control bus driver
Install the ProSafe-RS software
End
060001E.ai
Figure Flow of Software Revision Upgrade

<6.1 Procedure for Updating Control Bus Driver> 6-3
6.1 Procedure for Updating Control Bus Driver

This section explains the procedure for updating the control bus driver.
n Flow of Control Bus Driver Update

The PC must be restarted after installing the control bus driver. The same command is used
when updating and performing a new installation.
Start updating
the control bus driver
Execute setup command
Restart the PC
End updating
the control bus driver
060101E.ai
Figure Flow of Update

n Procedure of Updating Control Bus Driver (Windows Vista/Windows

Server 2008)
2. Set the ProSafe-RS installation CD-ROM to the drive. If the installer of .NET or ProSafe-
RS is automatically started, you need to terminate it by clicking [Cancel].
3. Find the Setup.exe under \COMDRV folder in the CD-ROM and run the program.
4. In the User Account Control dialog box that appears, click [Continue].
060103E.ai
Figure Install/Uninstall-Selection Dialog Box (Updating)
TIP
If the latest version of control bus driver is already installed, the install/uninstall-selection dialog box appears with
the [UNINSTALL] option selected and you cannot select [INSTALL]. In this case, click [Cancel] to finish the task.
6. In the dialog box confirming the installation, click [OK] to continue.

7. Windows Security dialog box for installing [Yokogawa Network Adapters] will be displayed.
060109E.ai
Figure Windows Security (Yokogawa Network Adapters)
9. A message appears indicating that the installation is complete (prompting a restart of the
PC). Click [OK] and remove the CD-ROM from the drive, then restart the PC.

n Detailed Procedure of Control Bus Driver Update (Windows XP/

IMPORTANT
Stop the operation of resident programs, including anti-virus software, if they are running, before
installation.
logon the PC.
2. Insert the ProSafe-RS installation CD-ROM into the CD-ROM drive.
3. Execute (CD-ROM drive name:) \COMDRV\setup.exe.
Vnet Driver Setup
Welcome
This program let you install or uninstall Vnet Driver.
INSTALL
Install Vnet Driver to you system.
UNINSTALL
Remove installed Vnet Driver.
OK Cancle
060105E.ai
Figure Install/Uninstall-Selection Dialog Box (Updating)
TIP
If the latest version of control bus driver is already installed, the install/uninstall-selection dialog box appears with
the [UNINSTALL] option selected and you cannot select [INSTALL]. In this case, click [Cancel] to finish the task.

5 In the dialog box confirming the installation, click [OK].



060104E.ai
6. In the Hardware Installation dialog box displayed, click the [Continue Anyway] button.
When a message appears indicating that the installation is complete (prompting a restart of
the PC), click [OK].
7. Restart the PC to finish the task.
TIP
If the control bus driver was previously installed from CENTUM CD-ROM, when installing control bus driver from
ProSafe-RS CD-ROM again, the following dialog box will be displayed.
Files Needed
The file 'bktdi.sys' on [Unknown] is needed.

OK
Cancel
Type the path where the file is located. and then click
OK.
Copy files from:

E:\CENTUM\COMDRV\tdi Browse...
060106E.ai
Figure Dialog Box
Under this circumstance, click [Browse] button on the dialog box so as to designate the path of the control bus
driver. The path for the control bus driver is as follows:
(CD-ROM Drive) :\COMDRV\TDI

<6.2 Revision Upgrade of ProSafe-RS Software (without Package Addition)> 6-8
6.2 Revision Upgrade of ProSafe-RS Software

(without Package Addition)
This section explains the procedure for upgrading the revision of the software without
adding new packages for a PC on which the ProSafe-RS software has already been
installed.
SEE
ALSO For the procedure to add packages while upgrading the revision, see the following:
n Item to be Prepared at Revision Upgrade (without Package Addition)

Prepare the following item so that it is at hand before upgrading the software revision without
adding packages.
ProSafe-RS software CD-ROM (CHSKM02): Containing the revision newer than the one
installed on the PC
n Preparation before Revision Upgrade (without Package Addition)

Restart the PC immediately before installation. It is not necessary to restart the PC if it has
already been restarted in the process of revision upgrade.

n Revision Upgrade (without Package Addition) Procedure

logon the PC.
4 If Microsoft .NET Framework 3.5 SP1 and Microsoft Visual C++ 2008 Redistributable have
not been installed, a dialog box appears, prompting you to install them. Follow the guidance
to install them. If you are required to restart the PC, then restart it.
5. The Welcome dialog box appears. Click the [Next] button. The Customer Information
dialog box appears.
TIP
If the version of the V net driver on the PC is older than the one on the ProSafe-RS CD-ROM, a dialog box
appears together with the welcome dialog box and requests you to update the driver.
Please update Vnet driver.
Yes No
060202E.ai
Figure Update V net Driver Dialog
If you select [Yes], the installation of ProSafe-RS will stop and you should first update the driver according to the
procedure. If [No] is selected, installation will continue but you should update the driver later.
7. Confirm the ID number in the ID Number dialog box and click the [Next] button.
Package List

Install to:
InstallShield
060201E.ai

Check the package list and click the [Next] button.
IMPORTANT
In the revision upgrade procedure, do not change the software installation destination folder. If it
is changed, some settings cannot be inherited and the software may not function properly.

installation.
11. Remove the CD-ROM from the CD-ROM drive and click the [Yes] button in the dialog box to
restart the PC. Click the [No] button to restart the PC later.
IMPORTANT
RS software.

<6.3 Revision Upgrade of ProSafe-RS Software (with Package Addition)> 6-11
6.3 Revision Upgrade of ProSafe-RS Software

(with Package Addition)
This section explains the procedure for upgrading the revision of the software with adding
new packages on a PC on which the ProSafe-RS software has already been installed.
SEE
ALSO For the procedure to upgrade the revision without package addition, see the following:
n Items to be Prepared at Revision Upgrade (with Package Addition)

Prepare the following items so that they are at hand before upgrading the software revision by
adding packages.
ProSafe-RS keycode FD for additional packages (CHSCM01)
ProSafe-RS software CD-ROM (CHSKM02): Containing a revision newer than the one
installed on the PC
IMPORTANT
When the revision of the software is updated by adding packages, all software corresponding
to the packages in the keycode FD and the packages already installed on the PC are installed
again.
n Preparation before Revision Upgrade (with Package Addition)

Restart the PC immediately before installation. It is not necessary to restart the PC if it has
already been restarted in the process of revision upgrade.

n Revision Upgrade (with Package Addition) Procedure

1. Logon to the PC as the administrative user that installed the ProSafe-RS.
IMPORTANT
Be sure to insert the keycode FD in the FD drive first and then insert the ProSafe-RS software
CD-ROM in the CD-ROM drive.

3. Insert the keycode FD containing codes for additional packages into the FD drive.
5. If Microsoft .NET Framework 3.5 SP1 and Microsoft Visual C++ 2008 Redistributable have
6. The Welcome dialog box appears, followed by a dialog box asking whether there is a
second keycode FD.
TIP
Yes No
060302E.ai
7. Click the [No] button if there is only one keycode FD.

If there are several keycode FDs, replace the keycode FD and click the [Yes] button. Click
the [No] button after inserting the last key code FD.
8. Click the [Next] button in the Welcome dialog box. The Customer Information dialog box
appears.

10. Confirm the ID number in the ID Number dialog box and click the [Next] button.
Package List

Install to:
InstallShield
060301E.ai
Check the package list and click the [Next] button.
IMPORTANT
In the revision upgrade procedure, do not change the software installation destination folder. If it
is changed, some settings cannot be inherited and the software may not function properly.

installation.
IMPORTANT
RS software.
n Tasks after Revision Upgrade (with Package Addition)

After the installation tasks are completed, it is possible to use Software Configuration Viewer
to put several keycode FDs together in one FD. By performing this task, it becomes possible to
install all the packages with a single keycode FD from the next installation.

<6.4 ProSafe-RS Software Version Upgrade> 6-14
6.4 ProSafe-RS Software Version Upgrade

In this section the procedure of ProSafe-RS software version upgrade will be explained.
The version upgrade installation means to upgrade from a lower version to a higher
version. For example, from R1.03 to R2.01 where the version number next to R is
increased by 1 or greater than 1.
n Items to be Prepared at Version Upgrade

Prepare the following items so that they are at hand before upgrading the software version.
Keycode FD for version upgrade installation (CHSCM01)
CD-ROM of ProSafe-RS Software (CHSKM02)
ProSafe-RS project ID license (CHSPJT-V11)
IMPORTANT
If the Microsoft .NET Framework 3.5 SP1 and Microsoft Visual C++ 2008 Redistributable
are not installed in the PC, a dialog box that prompts you to install them appears after you
start the version upgrade installation. Be sure to install them.
It is recommended that you do not change the destination folder of the version upgrade
installation. If you changed the destination folder, some of the previous setting may not be
properly inherited.
n Before Version Upgrade Installation and Version Upgrade Installation

Procedure
The version upgrade procedure and preparations for version upgrade installation are the same
as for the revision upgrade (with package addition) installation.
SEE
ALSO For more information about revision upgrade installation (with additional packages), see the following:
n Preparation before Revision Upgrade (with Package Addition) in 6.3, Revision Upgrade of ProSafe-RS
Software (with Package Addition)

<6.5 Settings after Upgrading ProSafe-RS Software> 6-15
6.5 Settings after Upgrading ProSafe-RS

Software
In this section, the settings after upgrading the ProSafe-RS software will be explained.
In general, the ProSafe-RS database and the SCS system programs are upward compatible.
Therefore, there is no need to modify the database after upgrading the ProSafe-RS software.
However, in order to enable the new features supported by the newer SCS system program, re-
creation of SCS Project or offline download of the database from SENG to SCS may be required
after upgrading the SENG.
IMPORTANT
The SENGs in the same RS project should have the software of the same release number.
Once opening an existing SCS project or creating a new SCS project using newer revision
software in SENG, the SCS project cannot be opened using older revision software.
The SCS system program release number of SCSs in a system should basically be
the same, but mixture of different release numbers is allowed. However, the SCSs
communicating with each other using the Inter-SCS safety communication function must
have appropriate release numbers to be compatible.
SEE
ALSO The SENG software release number, SCS system program release number, and information about compatibility
in inter-SCS safety communication between revisions in each software release are described in the cautionary
notes for upgrading. For more information about each release, see the corresponding section in the following:
TIP
If your PC does not satisfy the following conditions, it is recommended that the software for viewing the online
manuals should be upgraded to the Adobe Reader of the recommended version written in this manual.
CS 3000 electronic documents are also installed.
Adobe Acrobat is installed.
SEE
ALSO For more information about upgrading the software for viewing the online manuals, see the following:
4.4, Online Manual Setting

n Settings after Upgrading Software

After upgrading the ProSafe-RS software, the following procedures need to be performed.
What procedure needs to be performed depends on what new features to be used. User needs
to run the following procedures in accordance with each guideline of the revision upgrade
procedure.
Procedure A: Opening SCS Projects
Procedure B: Master Database Off-line Download
Procedure C: Creating New SCS Project and Off-line Download
Procedure D: Setting Definition Items for New Features and Off-line Download
Procedure E: Clean Project, Build and Off-line Download
Procedure F: Setting Definition Items for New Features, Clean Project, Build, and Off-line
Download
SEE
ALSO For more information about upgrading procedure to use the new features of each revision, see the following:
Generally, after upgrading the software, only Procedure A needs to be performed.
l Procedure A: Opening SCS Projects

After installing the latest revision of software in SENG, use SCS Manger to open the existing
SCS projects created by the older revision software.
IMPORTANT
The newer revision SCS Manager can simply open the SCS project created by the older
revision SCS Manager.
However, the project created by the older revision workbench can not be opened in the
Read-Only status. It is necessary to open the SCS project in the Read-Write status.
To open the project with password, the password needs to be entered and then open the
project in the Read-Write status.
It is necessary to use the newer revision SCS Manager at least once to open the library
created by older revision SCS Manager.
Procedure A must be done for the SCS projects of all the SCSs that mutually perform inter-
SCS safety communication. Otherwise, an error may occur during build.

l Procedure B: Master Database Off-line Download
For using the new features, this procedure may be necessary.
After upgrading SENG, then off-line download to the SCS using Master Database Off-line
Download.
The outline of the procedure is as follows:
1. Run Procedure A.
2. Off-line download to the SCS using Master Database Off-line Download.
SEE
ALSO For more information about the procedure of Master Database Off-line Download, see the following:
9.3, Master Database Off-line Download of the Engineering Reference. (IM 32S04B10-21E)
l Procedure C: Creating New SCS Project and Off-line Download

For using the new features, this procedure may be necessary.
After upgrading SENG, create a new project or remake the existing project and then off-line
download the project.
The procedure is the same as creating a new SCS project. And it is roughly as follows:
1. Create a new project and enter all the project settings.
The existing SCS project can be upgraded to a later revision using Import/Export functions.
Upgrading SENG to a newer revision and creating a new project, the whole existing project
data can be transferred to the new project.
SEE
ALSO For detailed procedures for transferring the existing SCS project using Import/Export functions, see the following.
2.19, Import and Export of the Engineering Guide (IM 32S01C10-21E)
2. Run build, and check the project data using Integrity Analyzer/Cross Reference Analyzer.
3. Off-line download the project.
SEE
ALSO For more information about off-line downloading,see the following:
9.1, Off-line Download of the Engineering Reference (IM 32S04B10-21E)
IMPORTANT
The SCS project and library created by an SENG in a revision later than the currently used
revision cannot be used.
The SCS project created or opened by a new revision of SENG cannot be opened by a
SENG in an earlier revision.
The library created or opened by a new revision of SENG cannot be added to the SCS
project of an earlier revision.

TIP
If the new SCS project uses a library, the library must be opened by a new-revision SCS Manager. However, if the
library POU uses FB/FU supported only by a new revision, create a new library.
Combination of SCS project and library revisions is explained below.
The procedures required for upgrading to a new revision:
If an SENG is upgraded to a new revision, you must follow the steps below to change the revision of SCS project /
library to the same software release number by opening all the SCS projects / libraries.
1. Open each original library projects to upgrade. Then, copy the library and paste it to the predetermined
folder, LIBRARIES, where the SCS project that uses the library is stored.
2. Open each SCS project to upgrade.
If a project-level password is required for opening SCS project and library, you have to enter the password and
open in ReadWrite mode in order to upgrade. If you dont know the password, contact the creator of SCS project
and library.
l Procedure D: Setting Definition Items for New Features and Off-line Download
Some new features require this procedure.
Install the new revision of SENG software, set the definition items for the new features, and off-
line download the project. The procedure is as follows:
1. Using SCS Manager, open the old-revision project.
2. Set the definition items for the new features. The items to be set are described in the section
of upgrading procedures for each software release number.
3. Run Build. Then run Integrity Analyzer and Cross Reference Analyzer for an approval
check.
l Procedure E: Clean Project, Build, and Off-line Download

Some new features require this procedure.
Install the new revision of SENG software, run Clean Project and Build for an existing project,
and off-line download the project. The procedure is as follows:
2. Run Clean Project.
check.
l Procedure F: Setting Definition Items for New Features, Clean Project, Build,
and Off-line Download
Some new features require this procedure. This procedure consists of Procedure D plus Clean
Project.
The procedure is as follows:
2. Set the definition items for the new features. The items to be set are described in the section
of upgrading procedures for each software release number.
3. Run Clean Project.
check.

<7. Troubleshooting> 7-1
7. Troubleshooting
This chapter explains probable causes of problems and actions to be taken.
n Note on Network Connection

On a Windows Vista/Windows Server 2008 PC, the Set Network Location dialog box may be
displayed when you connect the network cable. In this case, choose [Work] on the dialog box to
continue.
070001E.ai
Figure Set Network Location Dialog Box

<7.1 Troubleshooting Related to Control Bus Driver> 7-2
7.1 Troubleshooting Related to Control Bus

Driver
This section explains how to handle problems related to installation and updating of a
control bus driver and removal of the VF702/VF701 card. It also explains the procedure for
deleting the control bus driver.
n Problems when Installing Control Bus Driver

Here, it is explained how to handle problems that may occur when installing a control bus driver.
l If Error Message Appears

An error message may appear if you install a control bus driver without restarting the PC after
deleting the previous control bus driver.
Vnet Setup
Vnet driver installation error.

Please try again after Vnet driver uninstallation.
OK
070101E.ai
Figure Error Message Appearing when Installing a Driver
In this case, restart the PC and then install the control bus driver.

n If Driver is Successfully Installed but it Does Not Recognize VF702/

VF701 Card
If you add a driver in a status where a VF702/VF701 card is actually mounted in the PC, but
Windows has not recognized it, the driver is installed assuming that no VF702/VF701 card is
mounted in the PC. When installed in this way, the driver operates as if there were no VF702/
VF701 card in the PC; the driver never accesses the VF702/VF701 card and thus cannot
communicate via the connected control bus.
In this case, delete the current driver, restart the PC and install the driver again.
The following shows the Computer Management window in the status where a VF702/VF701
card is recognized.
Computer Management
Computer Management (Loal) DOCEP2

System Tools Computer
Event Viewer Disk drives
Shared Folders Display adapters
Local Users and Groups DVD/CD-ROM drives
Performance Logs and Alerts Floppy disk controllers
Device Manager Floppy disk drives
Storage Human Interface Devices
Removable Storage IDE ATA/ATAPI controllers
Disk Defragmenter Keyboards
Disk Management Mice and other pointing devices
Services and Applications Other devices
PCI Serial Port
Network Controllers
Monitors
Network adapters
Broadcom NetXtreme 57xx Gigabit Controller
Yokogawa Vnet/Lnet Adapter
Ports (COM & LPT)
Processors
Sound, devices
System devices
Universal Serial Bus controllers
070102E.ai
Figure Status where VF702/VF701 Card is Recognized (before Driver Installation)

n If Driver is Successfully Installed but Does Not Start

The driver may not start normally due to wrong connection of the bus or mistakes in address
setting. In this case, VLNIC errors are recorded in the [System] log of Event Viewer.
070103E.ai
Figure Event Viewer Recording VLNIC Errors (System)
Double-click a VLNIC error to display the Event Properties dialog box.

Select Friendly View Error code
070104E.ai
Figure Event Properties

Look up the error code in the table below. If the problem is caused by the bus configuration and/
or address setting, confirm that the settings are correctly made and shut down the PC. Then start
up the PC again.
Table Error Codes Generated when Starting Driver
Code Meaning
000101** RAM parity error (failure of VF702/VF701/VI702/VI701 card)
000102** RAM read/write error (failure of VF702/VF701/VI702/VI701 card)
000109** Address overlap error
00010a** Bus configuration error (wrong bus connector connection)
00010b** Dip switch station number parity error
00010c** Dip switch domain number parity error
00010d** Inappropriate dip switch station number setting
00020013 Illegal station number (may be detected in the case of bus connector connection mistakes)
Note: In the code, a 2-digit number 00 is displayed at the position of ** for VF702/VF701 while others for VI702/VI701.
Other causes of the driver not starting can be failure of the control bus interface card or conflicts
with other devices.
Please try replacing the control bus interface card, removing other devices from the PC, etc.
n If Blue Screen or Reboot Occurs when Installing Driver

Install the driver according to the following procedure.
1. Delete the driver.
2. Restart the PC.
3. Press the [F8] key when the message For troubleshooting and advanced options for
Windows, press F8 appears.
4. Select [Safe mode] from the [Windows advanced options] menu.
5. Log on as an administrative user when the log on screen appears.
6. Install the driver according to the normal installation procedure.
7. After installing the driver, restart the PC and start up in the normal mode.
TIP
In the safe mode, only basic files and drivers (mouse, monitor, keyboard, bulk memory, basic video functions,
default system services and network connection) are loaded. This is useful when a control bus driver cannot be
installed due to the presence of preinstalled modules, etc.
n If Installation is not Finished and Looping Occurs during Driver

Installation
Install the driver again according to the same procedure as above.

n Problems when Updating Control Bus Driver

This section explains how to handle problems that may occur when updating a control bus driver.
l If Blue Screen or Reboot Occurs when Updating Driver
SEE
ALSO For the procedure to solve this problem, see the following:
If Blue Screen or Reboot Occurs when Installing Driver
l If Installation is not Finished and Looping Occurs during Driver Installation
SEE
ALSO For the procedure to solve this problem, see the following:
If Blue Screen or Reboot Occurs when Installing Driver
n Procedure for Deleting Control Bus Driver

This section explains the procedure for deleting a control bus driver.
IMPORTANT
Whenever you delete a control bus driver, restart the PC before installing the driver again.

2. Insert the ProSafe-RS installation CD-ROM into the CD-ROM drive.
3. Execute Setup.exe in the COMDRV folder in the installation CD-ROM.
In Windows Vista/Windows Server 2008 environment, if a User Account Control dialog box
is displayed, click [Continue].

070107E.ai
Figure Install/Uninstall-Selection Dialog Box
TIP
If the control bus driver is not installed, the install/uninstall-selection dialog box appears with the [INSTALL] option
selected and you cannot select [UNINSTALL]. In this case, click [Cancel] to finish the task.

6. When a message appears indicating that the uninstallation is complete (prompting a restart
of the PC), click [OK].
7. Restart the PC.
n If PC is Restarted without Removing VF702/VF701 Card from PC after

Deleting Driver
If you restart the PC without removing the VF702/VF701 card from the PC after deleting a control
bus driver, Windows judges that the VF702/VF701 card is a newly added device and prompts
you to install a driver. In this case, do not add the driver according to the instructions on the
screen. If you install the driver according to the instructions on the screen, only the control bus
adapter driver is installed, whereas the control bus protocol driver is not installed.
This phenomenon may occur in the following cases.
The control bus driver was installed after deleting a network control device (actually a
VF702/VF701 card) of another device when installing and deleting devices.
The control bus driver was installed after deleting a control bus adapter driver only.

<7.2 Windows Related Troubleshooting> 7-8
7.2 Windows Related Troubleshooting

This section explains how to handle problems related to Windows.
n If Errors Occur in Other Adapters and Devices (e.g. Sound Board and
SCSI Board)
l Cause
An IRQ (Interrupt Request) conflict occurred between a control bus interface card and another
device.
l Actions
A VF701/VI701 card is a PCI card and may cause a conflict if the same IRQ as set for an ISA
card is used. In such cases, carry out one of the following procedures.
Change the IRQ setting of the ISA card to an unused number.
Change the IRQ of the network card in the BIOS setting of the PC. Alternatively, use the
utility that comes with the network card to make changes (effective in the case of a PCI
card).
Remove the ISA card.
n If Ethernet Communication is Disabled
l Cause
Mistakes in network bind settings
Mistakes in TCP/IP communication setting (e.g. IP address and subnet mask)
l Actions
Check the hardware, Ethernet adaptor card and Ethernet cable.
Check the settings of [Network Connections] in Control Panel.
n If Operation of Normally Operating PC Becomes Unstable
l Cause
Software not allowed to coexist with ProSafe-RS is installed.
l Action
Uninstall either the existing software or the newly installed software.
SEE
ALSO For software that is allowed to coexist with the ProSafe-RS software, see the following:
Software Operation Environment in 1.1, Overview on Software Installation
n If the System Locks Up

Please contact YOKOGAWA.

<7.3 ProSafe-RS Software Installation Troubleshooting> 7-9
7.3 ProSafe-RS Software Installation

Troubleshooting
This section explains how to handle problems that may occur when installing the
ProSafe-RS software. Moreover, it explains how to uninstall the ProSafe-RS software,
which may be required to handle problems caused by installing the ProSafe-RS software.
n If ProSafe-RS Software does not Operate Properly even after

Reinstallation
If you inadvertently delete part of the ProSafe-RS software, the software may not function
properly even if you reinstall the ProSafe-RS software as a recovery measure.
In this case, uninstall the ProSafe-RS software and upgrade the revision (without package
addition).
SEE
ALSO For the procedure for revision upgrade (without package addition), see the following:

<7.3 ProSafe-RS Software Installation Troubleshooting> 7-10
n Uninstalling ProSafe-RS Software

In the procedure explained here, the ProSafe-RS software is not uninstalled completely. To
uninstall the software completely, it is necessary to reinstall the OS.
IMPORTANT
Do not uninstall the software with this procedure unless it is instructed to do so by the installation
procedure.
l Procedure to Uninstall Software

Follow the procedure below to uninstall the ProSafe-RS software.
logon the PC.
3. Open Control Panel from Windows Start menu, and then choose the following:
Windows Vista/Windows Server 2008: Programs and Features
Windows XP/Windows Server 2003 : Add or Remove Programs
4. Select [ProSafe-RS] from the list of programs installed on the PC.
5. Click the [Delete] button.
The software is deleted and the progress is displayed.
TIP
The following items are not deleted by using [Add/Remove Programs] or [Programs and Features]:
ProSafe-RS related registries
Services registered for ProSafe-RS
Files created and modified using the ProSafe-RS software
6. Restart the PC when the dialog box showing the progress is closed.

<7.4 Troubleshooting Related to Vnet/IP Open Communication Driver> 7-11
7.4 Troubleshooting Related to Vnet/IP Open

Communication Driver
This Section describes the troubles at Vnet/IP Open Communication Driver.
n Troubles Occurred when Adding or Removing Vnet/IP Open

Communication Driver
This section describes how to handle the troubles that occurred when adding or removing the
Vnet/IP Open Communication driver.
l When VI702/VI701 Card is not Installed

When installing or removing the Vnet/IP Open Communication driver on a PC, the VI702/VI701
card must be installed in the PC. Otherwise a warning message will be displayed. In this case,
you need to install the VI702/VI701 card to the PC and then add or remove the driver.
l If the User is Not an Administrative User

In Windows Vista/Windows Server 2008 environment, if a user other than the administrative user
starts to install or uninstall the Vnet/IP Open Communication driver, a UAC dialog box shown as
follows will be displayed. On this dialog box, click [Cancel] and then logon as administrative user
and then run installation or uninstallation again.
070402E.ai
Figure UAC Dialog Box
l Double Starting
An installer (or uninstaller program) of Vnet/IP Open Communication driver cannot be double
started. When double starting an installer or uninstaller program, a warning message will be
displayed.
Click [OK] on the message box so as to terminate the later started installer or uninstaller program
and let the first started installer or uninstaller to continue.

<7.4 Troubleshooting Related to Vnet/IP Open Communication Driver> 7-12
n Troubles Occurred when Adding Vnet/IP Open Communication Driver

How handle the troubles occurred when adding the Vnet/IP Open Communication driver will be
explained in this section.
l When the Error Message is Displayed

During installation, an error message may be displayed as follows. If you have clicked [Dont
Install] button, this error message may appear. Then you need to run the installation again.
070401E.ai
Figure Error Message
An error message different from the above figure may also be displayed. In this case, you need
to click [OK] button.
If you have not clicked [Dont Install] button, but you have reinstalled the Open Communication
driver right after deleting it without restarting the PC, then delete the Vnet/IP Open
Communication driver if you can delete it, and then reinstall the driver after restarting the PC.
n Deleting Vnet/IP Open Communication Driver

The problems may be encountered when deleting the Vnet/IP Open Communication Driver are
explained below:
l PC Restarted after Deleting Vnet/IP Open Communication driver without

removing the VI702/VI701 from the PC
If Vnet/IP Open Communication Driver is deleted and the PC is restarted without removing the
VI702/VI701 adapter from the PC, Windows will deem that VI702/VI701 is a new device so as to
prompt for installing the driver for it.
In this case, do not install the driver and ignore the prompted instructions.

<8. Backup> 8-1
8. Backup
It is recommended to back up the system regularly to prepare for unexpected problems.
According to the purpose, specific folders can be selected as targets of backup.
The table below shows relationship between the purposes of backup and backup target
folders.
Table Relationship between Purposes of Backup and Target Folders

Purpose Folder Registry Remark
Backing up the entire Windows
Please carry out backup tasks after closing
system when installation and Entire hard disk All
all applications.
startup are completed
Please carry out backup tasks after closing
ProSafe-RS engineering data SCS project folder
the SENG software.
When the standard model of PC hardening has been selected, you need to logon to the PC with
a user account that is authorized to access the ProSafe-RS related folders to perform backups.
n Backup of Entire Windows System

Back up the Windows system using commercially available software to prepare for disk failures.
n Backup of Windows
It is recommended to use commercially available software to back up the Windows operating
system files.
n Backup of Projects
ProSafe-RS folders can be backed up by copying them to a storage medium via Windows
Explorer. Moreover, they can be backed up using commercially available backup software.
Back up SCS project folders using Version Control Tool.
SEE
ALSO For Version Control Tool, see the following:
13, Version Control of the Engineering Reference (IM 32S04B10-21E)

<8. Backup> 8-2
n Creating Windows Recovery Disk

There are cases where Windows may become unable to start up or logon may be prohibited if
certain applications are installed. To deal with such cases, you should have system recovery
disks and startup disks in order to be able to recover the system status to the point when these
disks were created.
After installing a program, or changing hardware configuration or changing system status, you
need to create a set of Repair Disk and Start Disk.
SEE
ALSO See the manuals related to Windows for the detailed explanation of the procedure to create the Windows
Recovery disks.
An example in Windows XP environment is as follows:
l Items to be Prepared
DOS formatted FD: 2 disks (one startup disk and one system recovery disk)
l Creation of System Recovery Disk

2. From the [Start] menu of Windows, select [Programs] - [Accessories] - [System Tools] -
[Backup], and then select [Emergency Repair Disk] to start the wizard.
3. Select the [Also backup the registry to the repair directory] check box in the dialog box
appearing in the middle of the Backup or Restore Wizard.
Backing up to the FD is started.
4. Remove the FD from the drive after the backup is completed.
l Startup Disk Creation Procedure

2. Format a FD.
3. Copy the following files under C:\ to the FD using Windows Explorer.
C:\BOOT.INI
C:\NTLDR
C:\NTDETECT.COM
If these files are not displayed under C:\, check [Show hidden files and folders] in the
[View] tab displayed by selecting [Folder Options] in the [Tools] menu of Windows Explorer
and then copy the folders.
4. Remove the FD from the drive after the copying is completed.
l Usage Procedure
If PC does not start up (when boot Information is damaged)
It is possible to start up the Windows from the FD drive using the startup disk.
Insert the startup disk FD in the FD drive and start up the PC.
In this case, the PC uses the boot information contained in the startup disk FD and the
system files and registries stored on the hard disk to start up.
If only boot information is damaged, it can be recovered by returning the 3 files copied when
creating the startup disk to C:\ on the hard disk.
If Windows behaves strange (when registries are damaged)
If the registries are damaged, start up the PC with the Windows setup FD and select
[System recovery]. In this case, a configuration storage disk is required; insert this FD in the
FD drive and recover the system.

<9. Compatibility between Revisions and Cautionary Notes for Upgrading> 9-1
9. Compatibility between Revisions and

Cautionary Notes for Upgrading
IMPORTANT
It is necessary to contact Yokogawa service agent before performing any operation explained in
this chapter.
It is necessary to backup the whole project before upgrading ProSafe-RS.
In this chapter, the compatibility and cautionary notes for upgrading the ProSafe-RS
software to each release number will be explained individually. Before upgrading the
ProSafe-RS, it is necessary to read all the related cautionary notes for release number
between the existing software and the upgrading software beforehand.
Information on the following upgrading is provided:
Upgrading the software with a release number older than R1.01.30 to R1.01.30.
Upgrading the software of R1.01.30 to R1.01.40/R1.01.50.
Upgrading the software of R1.01.30/R1.01.40/R1.01.50 to R1.02.
Upgrading the software of R1.02 to R1.03
Upgrading to R1.01.30 is explained in section 9.1.

Upgrading to R1.01.40/R1.01.50 is explained in section 9.2.
Upgrading to R1.02 is explained in section 9.3.

<9.1 Upgrading to R1.01.30> 9-2
9.1 Upgrading to R1.01.30

The cautionary notes for upgrading the ProSafe-RS from an earlier version to R1.01.30 will
be explained below.
IMPORTANT
When subsystem communication or SYS_SEC_CTL FB are applied while ProSafe-RS R1.01.30
is integrated with CS 3000, the release number of CS 3000 software must be R3.07 or later.
V net Driver
Install the V net driver included in the CD-ROM of ProSafe-RS software.
However, for the HIS with the CS 3000 software R3.07 environment, installation of the driver
is not needed.
n Software Revisions
Software revision information in release R1.01.30 and in the earlier releases is as follows:
Software Release R1.01.00
SENG software release number: R1.01.00
SCS system program release number: R1.01.00
l Inter-SCS Safety Communication

The release numbers of the SCS system programs on SCSs communicating with each other
using the Inter-SCS safety communication function must be the same.
n Procedures for Upgrading

When using the added and upgraded features of R1.01.30, install the ProSafe-RS R1.01.30
or later version of software to SENG and open existing SCS projects. Then the following new
features of R1.01.30 are applicable.
SCS information Dialog box
Saves and downloads the operation marks
Locks user-defined FB parameters
SEE
ALSO For more information about opening an existing SCS project, see the following:
l Procedure A: Opening SCS Projects in n Settings after Upgrading Software in 6.5, Settings after
Upgrading ProSafe-RS Software.

<9.1 Upgrading to R1.01.30> 9-3
n Cautions on Using Added and Upgraded Features

In order to use the added and upgraded features of R1.01.30, it may be required to perform
offline downloading to the SCS. The related procedures are as follows.
SEE
ALSO For more information about settings after upgrading, see the following procedures in:
n Settings after Upgrading Software in 6.5, Settings after Upgrading ProSafe-RS Software.
l Procedure B: Master Database Off-line Download
l Procedure C: Creating New SCS Project and Off-line Download
l Subsystem Communication (Modbus Communication Package)

When performing the engineering works to apply the Modbus communication package (for
ALR111, ALR121) on SCS, Procedure C should be performed on R1.01.30 or later version
SENG. On the SCS State Management Window of SCS maintenance Support Tool and on the
SCS Status view of the CENTUM HIS that has been integrated with ProSafe-RS, the status of
Comm. I/O Lock will be displayed with [No] until the off-line download is completed.
l Using the FU/FB Added in R1.01.30

In order to use the added FU/FB of R1.01.30 such as SYS_SEC_CTL (for changing SCS security
level), Procedure C should be performed on R1.01.30 or later version SENG.
l Forcing (SCS Security Level 0)

From R1.01.30, when SCS security level is 0, the values of internal variables and FB parameters
can be changed without locking the variable or parameter. However, this change is not valid if
Procedure B is not performed on R1.01.30 or later version SENG.
l I/O Lock Window

In R1.01.30 version, the process of getting data from SCS and displaying them on I/O Lock
window is changed. This change will become valid after Procedure B is performed on R1.01.30
or later version SENG.
IMPORTANT
After upgrading SENG to R1.01.30 or later version, for the first time off-line download to an SCS
is performed while the SCS is running inter-SCS communication with other SCSs, the Procedure
B needs to be performed on R1.01.30 or later version SENG for all the communicated SCSs.
When off-line download to the SCS that is running inter-SCS communication with other SCSs, it
is necessary to take measures on the other SCSs so as not to cause a nuisance tripping.
l SCS Start Action when Applied with IRIG-B

In R1.01.30 version, the SCS start action is changed under the circumstance that the SCS is
applied with IRIG-B but the IRIG-B receiver is not connected. This change will become valid after
Procedure B is performed on R1.01.30 or later version SENG.

<9.1 Upgrading to R1.01.30> 9-4
l Handling Messages during SCS Start
In R1.01.30 version, how the SCS during start handles the SOE data and diagnostic messages
occurred before SCS stopped is changed. This change will become valid after Procedure B is
performed on R1.01.30 or later version SENG.
IMPORTANT
When the SCS is restarted by Master Database Off-line Download, the Diagnostic Information
Window should be closed. If the window is not closed during off-line download, it is necessary
to click [Update] button when the SCS start action is completed so as to display the diagnostic
information properly.
n Cautionary Notes for Executing Build after Upgrading SENG

If a user-defined FU satisfying the following conditions is created by an SENG in an earlier
version than R1.01.30 and the SENG is upgraded to R1.01.30 or later, the first Build execution
after the upgrade will cause a Build Error message.
This is because the specification change made in the R1.01.30 to prevent the creation of the
user-defined FUs satisfied the following conditions.
l Conditions that Cause a Build Error

FB(s) is used in a user-defined FU.
Variable(s) of global attributes is used in a user-defined FU.
l Workaround
If an FB or global variable(s) is used in a user-defined FU, change the user-defined FU to a user-
defined FB. An off-line download is required after this change.
n Notes on Running Cross Reference Analyzer after Upgrading SENG

If a user-defined FU satisfying the following condition is created by an SENG in an earlier
version than R1.01.30 and the SENG is upgraded to R1.01.30 or later, the message Instruction
Modified appears at the execution of Cross Reference Analyzer after the initial Build execution.
l Condition for an Instruction Modified Notification

If local variable(s) is used in a user-defined FU.

<9.1 Upgrading to R1.01.30> 9-5
l Background
The following specification change was made in R1.01.30.
Table Specification Change
If local variable(s) is used in a user-defined FU, local variable(s) is not initialized every time the
Before
user-defined FU is called.
If local variable(s) is used in a user-defined FU, local variable(s) is initialized every time the user-
defined FU is called.
The value used for initialization is the initial value defined in Dictionary.
If initial value is not defined in the Dictionary, value will be initialized using the following:
After
DINT type: 0
REAL type: 0.0
BOOL type: FALSE
TIME type: t#0s
Local variables in a user-defined FU are initialized every time the user-defined FU is called.
Notes
If local variables are used in a user-defined FU, set values to local variables in advance.
l Workaround
Check if the Instruction Modified message was caused by the specification change, and modify
the application logic if necessary.
n Cautions on On-line Change Downloading after Upgrading SENG

After upgrading SENG from R1.01.10 to R1.01.30 or later version, the first time on-line download
will download all POUs to SCS. Therefore, when running build, a warning message for locking all
the outputs will be prompted.
For the later On-line Change Download, it will download only the modified POU to SCS.
It is recommended to run off-line download or on-line change download right after the upgrading.
Thus, the On-line Change Download for the later modifications can download only the modified
POU to SCS.
Follow the procedures below to perform either off-line downloading or on-line change download
right after upgrading.
l Off-line Download
1. Choose [Clean Project/Library] from [Project] menu.
2. Start [Build].
3. Run off-line downloading.
l On-line Change Download

1. Choose [Edit Project Description] from [Tools] menu and then click [OK] on the displayed
Project description dialog box.
2. Save the project.
3. Start [Build] (a warning message for locking all the outputs will be prompted).
4. Run On-line Change Download.

<9.2 Upgrading to R1.01.40/R1.01.50> 9-6
9.2 Upgrading to R1.01.40/R1.01.50

In this section, the cautionary notes for upgrading to R1.01.40/R1.01.50 will be explained.
Moreover, for upgrading from a release older than R1.01.30 to R1.01.40/R1.01.50, it is
necessary to read the cautionary notes for upgrading to R1.01.30 together with this
section.
SEE
ALSO For more information about upgrading from a release older than R1.01.30 to R1.01.30, see the following
9.1, Upgrading to R1.01.30
Software revision information in release R1.01.40 is as follows:
Software revision information in release R1.01.50 is as follows:

The release numbers of the SCS system programs on SCSs communicating with each other
using the Inter-SCS safety communication function must be the same.

For upgrading from R1.01.30 to a newer version, the ProSafe-RS software needs to be installed
into SENG. However, no specific operation is needed for applying the revised and added
features after the installation.
The SCS project and library created or edited in R1.01.30 will be unconditionally converted to
R1.01.40/R1.01.50 when they are first time opened after upgrading to R1.01.40/R1.01.50. There
will be no confirmation dialog box prompts for the conversion.
IMPORTANT
When upgrading from a release older than R1.01.30 to R1.01.40/R1.01.50, the cautionary notes
for upgrading an earlier release to R1.01.30 should be referenced. It is necessary to read all the
cautionary notes and then perform the required operations accordingly.

<9.2 Upgrading to R1.01.40/R1.01.50> 9-7
n Note on Upgrading to R1.01.50

If a user-defined FB satisfying the following condition is created by an SENG in an earlier version
than R1.01.50 and if the SENG is upgraded to R1.01.50 or later and a Build is performed without
modification of the project data, there are cases where an off-line download is required.
l Condition
With POU (program or user-defined FU /FB) created by FBD, if the output of an FU/FB is looped
back to its own input parameter, a variable must be placed in the loop.
OR
IN
OUT
090201E.ai
Figure Example of Correct Loopback
If a user-defined FB ignoring this rule meets one of the following conditions, an off-line download
is required.
(Condition 1)
If the Generate symbols monitoring information for the user-defined FB is OFF.
(Condition 2)
If the input of the loopback is the output from the FB. (B is FB in the following figure)
A
b01 B
b03
b02
090202E.ai
Figure Example of Loopback Requiring an Off-line Download
l Background
With a SENG in an earlier version than R1.01.50, there are cases where no warning message is
output at a Build execution for a POU that does not follow the loopback rule.
With a SENG in R1.01.50 or later, the following warning message is always output at a Build
execution for a POU that does not follow the loopback rule.
WARNING: Used of loop is not recommended.
If this message appears for a POU after the SENG is upgraded to R1.01.50 or later, place a
variable in the loop.

<9.3 Upgrading to R1.02> 9-8
9.3 Upgrading to R1.02

In this section, the cautionary notes for upgrading from R1.01.30, R1.01.40, or R1.01.50 to
R1.02 will be explained.
Moreover, for upgrading from a release older than R1.01.30 to R1.02, it is necessary to
read the cautionary notes for upgrading to R1.01.30 together with this section.
IMPORTANT
In order to use the new features when the ProSafe-RS R1.02 is integrated with CS 3000, the
release number of the CS 3000 software must be R3.08 or later.
Software revision information in release R1.02 is as follows:
Software Release R1.02.xx (*1)
SENG software release number: R1.02.xx (*1)
SCS system program release number: R1.02.xx (*1)
*1: xx varies in accordance with the last two digits of the release number for the software released between R1.02.00 and R1.03.00.

The release number of the SCS system program on the Inter-SCS safety communication with an
SCS in R1.02 must be R1.01.30 or later.
If Vnet/IP is used for route of the Inter-SCS safety communication, the system programs on the
SCSs must be in R1.02.

In order to use the added or modified features in the R1.02, install the R1.02 or later software and
open the existing SCS Project. This will allow you to use the following added/modified features
in R1.02.
Alarm Off
Modified On-line Change Download
SEE
ALSO For cautionary notes for opening the existing SCS Project, see the following:
Upgrading ProSafe-RS Software

l Cautionary Notes for On-line Change Download after Upgrading the SENG to
R1.02 or Later
After upgrading an SENG to R1.02 or later and if you use the SENG for engineering the project
data created by an SENG in an earlier version than R1.02, execute Build first without changing
any parameter, then perform an on-line change download.
If you skip executing operation above and do the following, there are cases where unchanged
POUs (Program Organization Units) are downloaded to SCS in the on-line change download.
From the Dictionary View window of the SCS Manager, Add, Delete, Sort the named global
instances of FB used by POUs.
Add or Delete an existing FU to/from POUs.
In the Link Architecture View window of the SCS Manager, Change the order of the user-
defined FU/FB.
TIP
The following warning message appears in the first Build execution after the SENG is upgraded to R1.02.
WARNING: POUs indexes are modified for next on line change. On-line change may download others POUs in
addition of the modified ones.
n Cautionary Notes on Using New Features

Some steps are required before using the new features in the R1.02. The steps and cautionary
notes for each feature are as follows.
SEE
ALSO For detailed procedures after the upgrade, see the following in the n Setup Procedures after Upgrading
Software in the section 6.5 Setups after Upgrading ProSafe-RS Software:
l Procedure B : Master Database Off-line Download
l Procedure C : Creating New SCS Project and Off-line Download
l Procedure D : Setting Definition Items for New Features and Off-line Download
l Support for Vnet/IP

For engineering the SCS connected with Vnet/IP, follow the Procedure C on SENG in R1.02 or
later.
l Optical ESB Bus Repeater

For extending the ESB bus using an Optical ESB Bus Repeater, follow the Procedure D on
SENG in R1.02 or later. Set the parameters from the [SCS] tab on the SCS Constants Builder.
l Using the New FBs in the R1.02

Before using the new FBs in the R1.02, follow the Procedure C on SENG in R1.02 or later.

l Outputting Process Alarm Messages when AOF is Released
From the SCS Constants Builder window, you can specify to (or not to) output the suppressed
process alarm messages when the AOF is released.
This setting is applicable when the ProSafe-RS is integrated with CENTUM.
Follow the Procedure D on SENG in R1.02 or later.
l Plant Hierarchy
For specifying Plant Hierarchy to the tag data operated and monitored on HIS when the ProSafe-
RS is integrated with CENTUM, follow the Procedure B on SENG in R1.02 or later.
l Expansion of Alarm Processing Levels

When the ProSafe-RS is integrated with CENTUM, you can set the Alarm Processing Levels (5
to 16) to the tag data operated and monitored on HIS.
Follow the Procedure D on SENG in R1.02 or later.
SEE
ALSO For detailed procedures, see the following:
2.1, Engineering on the SENG Side of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
l Newly Supported I/O Modules (SAI143-H, SAI533, SDV541)

In order to use the I/O Modules newly supported by the R1.02, you must follow the Procedure C
on SENG in R1.02 or later.


In this section, the cautionary notes for upgrading from R1.02 to R1.03 will be explained.
Before you upgrade, read also the cautionary notes for the previous revisions issued after
the software version currently installed on your PC.
IMPORTANT
In order to use the new features when the ProSafe-RS R1.03 is integrated with CS 3000, the
release number of the CENTUM CS 3000 software must be R3.08.50 or later.
*1: xx varies in accordance with the last two digits of the release number for the software which will be released after R1.03.00.

The release number of the SCS system program to perform Inter-SCS safety communication
with an SCS in R1.03 must be R1.01.30 or later.
SCSs must be in R1.02 or later.

In order to use the added or modified features in the R1.03, install the R1.03 or later software and
open the existing SCS Project.
SEE
n Cautionary Notes on Using New and Modified Features

Some steps such as an off-line download to SCS may be required before using the new features
in the R1.03 after the SENG software is upgraded to R1.03. The steps and cautionary notes for
each feature are the followings.
SEE
ALSO For detailed procedures after the upgrade, see the following in the n Setup Procedures after Upgrading
Software in the section 6.5 Setups after Upgrading ProSafe-RS Software:
l Procedure D : Setting Definition Items for New Features and Off-line Download

l Test Function (i.e. SCS Simulator that Runs on a PC) and Interface for Plant
Training
Before using the Test function (i.e. SCS simulator), you need to complete the Procedure C. You
cannot download the project created for SCS simulation tests to an actual SCS.
CS 3000 system must be upgraded to R3.08.50 or later.
l New Input/Output Modules (SDV521, SDV531-L)

Before using the Input/Output modules newly supported by R1.03, you need to complete the
Procedure C.
l New Optical ESB Bus Repeater Modules (SNT411/SNT511)

Before using the Optical ESB Bus Repeater Modules newly supported by R1.03, you need to
complete the Procedure D. You need to set parameters using the SCS Constants Builder and
I/O Parameter Builder.
SEE
ALSO For setting parameters for Optical ESB Bus Repeater Modules, see the following:
n SCS Tab in 3.1.3, SCS Constants Builder of the Engineering Reference (IM 32S04B10-21E)
n Items Set for Nodes in 4.4, I/O Parameter Builder of the Engineering Reference (IM 32S04B10-21E)
TIP
For using SNT411/SNT511, SCP451 (processor module) which supports the SNT411/SNT511 needs to be
prepared. For further information, please contact our sales office.
l Using the New FBs in the R1.03

Before using the new FBs in the R1.03, follow the Procedure C on SENG in R1.03 or later.
l For Using the On-line Change Function for Input/Output Module Channels
Before using the On-line change function for Input/Output module channels, you need to
complete the Procedure B.
l SCS Link Transmission

Before using the SCS Link Transmission, you need to complete the Procedure C.
TIP
If you use SCS Link Transmission on SCS-IP, you need to have the SCP451 which supports SCS Link
Transmission. If you use SCS Global Switch Communication via Vnet/IP, you may need to update the CPU
module of the FCS of CENTUM. For further information, please contact our sales office.

l Grouping Override FB
Before using the Grouping override FB, you need to complete the Procedure C.
l Structured Text (ST)

For using the ST language in ProSafe-RS, you need to complete the Procedure D. Use the
Multi-Language Editor to create application in ST.
l Password FB
Before using the upgraded Password FB in R1.03, you need to complete the Procedure B.
l Enhanced CENTUM Integration for ANLG_S

Before using the enhanced CENTUM Integration in R1.03 for the ANLG_S block, you need to
complete the Procedure C.
n Notes on Upgrading SCS Project in R1.02 to R1.03 or Later

With the SCS project created in R1.02, no data status is attached to the PV of the mapping block
S_ANLG_S for ANLG_S. But in R1.03 or later, a data status is attached to the PV of the mapping
block S_ANLG_S.
In R1.03 or later, if the status of IN terminal of ANLG_S FB for the mapping block S_ANLG_S
turns BAD, the data status of PV for S_ANLG_S turns BAD (0x8000 0000). (Default in the SCS
Constants Builder)
Therefore, if the PV of S_ANLG_S is referred via FCS or OPC, the behavior may change
between the SCS project created newly in R1.03 or later and the SCS project created in R1.02.
If you want the same behavior as that in R1.02, set [PV Status of S_ANLG_S] in the SCS
Constants Builder to [NO].
n Notes on Enhanced Integrity Analyzer
l Stricter Check of Recursive Call in POU

Before R1.03, there are cases where a POU containing recursively called FB and FU can be
downloaded to SCS. In R1.03 or later, an error is raised for a POU with recursive calls to prevent
its download to SCS.
The error detection depends on how the recursive call is implemented: during generation or by
Integrity Analyzer.
When upgrading to R1.03 or later, make sure that no recursive call is included in POU. If any,
change the logic to exclude the recursive call from the POU.
TIP
Before R1.03, this does not cause an error during Generation. Even if a Warning is displayed by Integrity
Analyzer, a download to SCS is allowed after the Warning is acknowledged.

l Notes on Comparison Operation (=, <>) on Floating-point Data
There are cases where comparison operation using = (equal) or <> (not equal) on floating-
point data does not produce expected results because a round-off error may result from repeated
arithmetic operations.
In R1.03 or later, if accurate comparison operation (=, <>) on floating-point data is detected,
Integrity Analyzer displays a warning.
After upgrading to R1.03 or later, if accurate comparison operation (=, <>) on floating-point data
is detected, a warning is displayed after the upgrade.
If a warning appears, check if the program needs to be enhanced using smaller than (<) or
greater than (>). If the result of the check is no need to change program, acknowledge the
warning that Integrity Analyzer displayed. This will enable a download of the program to SCS.
n Notes on Changed Password FB

If a wrong password for the Password FB is entered from HIS, the behavior in R1.03 or later is as
follows:
Table Change made to Password FB
Version Change in behavior if a wrong password is entered for Password FB
In the operation to change MV in the Password FB, if user enters a wrong password, a system
alarm is raised, and user has to undo the change MV to the previous value.
Before R1.03
If a wrong password is entered, a diagnostic information message is displayed to notify it.
Here, the changed MV value remains as is and an ANS+ or ANS- process alarm is raised.
If a wrong password is entered, an error message for the wrong password is displayed in the
R1.03 or later
dialog box on HIS, and the MV value remains unchanged.
n Notice on the Variables Begin with Underscore Characters

From R1.03, the variable and the Defined Words begin with underscore character will be handled
differently by the system.
l Specification Prior to R1.03

Prior to R1.03, to start the variable or the Defined Words with underscore character is prohibited,
however, if you started the variable or the Defined Words with underscore character, no error
would be indicated.
l Specification for R1.03 or Later

Since R1.03, the variable or Defined Words begin with underscore character can be used,
however, if they are identical with system reserved words, an error will be indicated. The system
reserved words are as follows.
System Reserved Words:
_AND, _CALL, _CALL_IEC_SFC_FB, _END, _GOTO, _IF, _NOT, _PUSH_PAR, _OR,
_POP_CSTK, _PUSH_CSTK, _RET, _STEP, _XOR


The notices on version upgrading from R1.03 to R2.01 (R2.01.10 or later) will be explained
in this section. Before upgrading installation, the documents regarding the currently
installed ProSafe-RS software as well as the release notes for the previous upgrading
installations should be read first.
In this section, the procedure for upgrading from R2.01.00 to R2.01.10 will also be
explained. If R2.01.00 is installed in your PC, you need to upgrade the software to
R2.01.10.
IMPORTANT
When integrating ProSafe-RS and CENTUM VP, the new features added to ProSafe-RS
R2.01 are supported only in CENTUM VP R4.01 and later versions.
If you plan to manage ProSafe-RS PCs in Windows domain environment, the Windows
domain environment settings should be performed before performing the installation.
Software Release: R2.01.xx (*1)
*1: xx stands for the revisions after releasing R2.01.00
*2: For R2.01.10, xx stands for 00

The earlier version of SCS can performs inter-SCS safety communication with the SCS that has
R2.01 system program must be a version of R1.01.30 or later.
If the inter-SCS safety communication is routing Vnet/IP, the two version of system programs in
the SCSs should be standardized to R1.02 or a later version.
l Control bus Drivers

The control bus drivers installed on the PC should be upgraded to the version supplied at R2.01
(R2.01.10). The ProSafe-RS R2.01 control bus drivers are compatible with the control bus drivers
provided in CENTUM VP R4.01.
n Basic Procedure of Upgrading Installation

When using the added or changed software features, the installation should be performed and
opening the existing SCS projects with the installed ProSafe-RS software of R2.01 or later
version.
SEE
ALSO For more information about opening or operating the existing SCS project, see the following:

n Cautionary Notes on Using New and Modified Features

When using the following features added in R2.01 software, SENG software needs to be
upgraded to R2.01. The procedure and the notices are explained as follows:
l Settings for PC Hardening

After installing ProSafe-RS R2.01 software, start Security Setting Utility to setup security settings.
When integrated with CENTUM VP and the Common Functions of ProSafe-RS Software are
installed in the same PC of CENTUM VP, the security settings also need to be defined with the
Security Setting Utility.
SEE
ALSO For more information about Security Setting Utility, see the following:
11, Security Setting Utility
When the standard model of PC hardening is selected in Security Setting Utility, the user
accounts for various privileges need to be created and added respectively to the proper user
groups.
SEE
ALSO For more information about the settings after selecting the standard model of PC hardening, see the following:
4.2, User Account and Folder Settings
n Procedure for Upgrading from R2.01.00 to R2.01.10

Carry out the following procedure to upgrade your system:
1. For a Windows Vista PC with no CENTUM VP software, install the Windows hotfix program
provided in the CD-ROM of R2.01.10.
SEE
ALSO For more information about the procedure for installing the Windows hotfix programs, see the following:
n Windows Hotfix Programs Installation in 3.1.1, Windows Setup (Windows Vista)
2. Update the control bus drivers using the ProSafe-RS software CD-ROM of R2.01.10.
3. Without using the key code FD, carry out installation to upgrade from R2.01.00 to R2.01.10.
This installation should be done by following the procedure for revision upgrading (without
package addition).
IMPORTANT
If any software package should be added, install it only after you have upgraded the system from
R2.01.00 to R2.01.10.


In this section, the cautionary notes for upgrading from R2.01 to R2.02 will be explained.
Before you upgrade, read also the cautionary notes for the previous revisions issued after
IMPORTANT
When integrating ProSafe-RS and CENTUM VP, the new features added to ProSafe-RS
R2.01 are supported only in CENTUM VP R4.02 and later versions.
If you plan to manage ProSafe-RS PCs in Windows domain environment, the Windows
domain environment settings should be performed before performing the installation.

l Control Bus Drivers

The control bus drivers installed on the PC should be upgraded to the version supplied at R2.02.

In order to use the features added or modified in R2.02, install the R2.02 or later software and
open the existing SCS Project.
SEE

9.6.1 Cautionary Notes for Upgrading
n Procedure for Using New and Modified Features

After the SENG software has been upgraded to R2.02, some of the features added or modified in
the R2.02 require further steps, such as off-line downloading to SCS, before they can be used. In
the following, the steps are explained for each feature.
SEE
ALSO For Procedure B and Procedure C mentioned in this section, see the following in n Setup Procedures after
Upgrading Software in 6.5, Setups after Upgrading ProSafe-RS Software:
l New I/O Module (SDV526)

To use the I/O module SDV526 newly supported in R2.02, you must perform Procedure C.
l Behavior of AIO/DIO modules at Online Change Download

To enable online change downloading with the target AIO/DIO module kept running when you
have changed any settings of I/O Parameter Builder that require downloading to the AIO/DIO
module (IOM download), you must perform Procedure B. If not, the target AIO/DIO module will
be stopped as before.
SEE
ALSO For the behaviors of AIO/DIO modules during online downloading with software before R2.02, see the following:
n Behavior of AIO/DIO Modules at Online Change Download in 9.6.2, Compatibility with Earlier
Revisions
l Showing the Results of the Last Analysis on Cross Reference Analyzer

To enable the function to show the results of the last analysis after you have upgraded SENG
to R2.02, you must once acknowledge the analysis results in Cross Reference Analyzer and
perform downloading to SCS.

n Notes on Online Change Download after Upgrading SENG

In R2.02, the problem that the FB for which you have specified a minus value for a label in a
CASE statement does not run properly (*1) has been fixed. Because of this, the behavior of
online change downloading after you have upgraded the SENG to R2.02 will be as follows.
After you have upgraded the SENG to R2.02, if you perform a build for a project created in a
version before R2.02 and execute online change downloading, all the FBs containing any CASE
statement in the ST language will be downloaded (*2) even if no changes have been made to the
logic. Once you rebuild a project of a version earlier than R2.02 on a R2.02 system and execute
online change downloading, FBs with no logic change will not be downloaded in the subsequent
online change downloading.
You can use the Database Validity Check Tool, as necessary, to find out which FBs will be
downloaded before you execute online change downloading.
In a revision before R2.02, FBs containing any CASE statement in which a minus value is
specified for a label do not run correctly, so they can be spotted and removed in the system test.
Therefore, no such FBs should exist in a project. However, if such FBs do exist, the FBs may
start to run normally after downloading.
To avoid such unexpected change in behavior, you should check the project to see if there are
any FBs containing a CASE statement in which a minus value is specified for a label.
If any FBs using a minus value for a label of CASE statement are found, make sure that the
change in behavior does not cause any adverse effects on the system. (*3)(*4)
If FBs using a minus value for a label of CASE statement are not found, all the FBs using
CASE statements will be downloaded but the system behavior remains the same; so you do
not need to perform tests again.
*1: If you specify a minus value for a label in a CASE statement in ST, an incorrect database which causes unexpected behavior
may be generated.
In the following example, if variable1 is neither 1 nor 2, 3 is always assigned to aaa.
CASE variable1 OF
1: aaa := 1;
2: aaa := 2;
-1: aaa := 3; (* When the variable1 is neither 1 nor 2, this line is always executed.*)
-2: aaa := 4;
ELSE aaa := 5;
END_CASE;
*2: In this case, Cross Reference Analyzer does not detect the difference of the FBs using CASE statements.
*3: In this case, Cross Reference Analyzer does not detect the difference of the FBs using a minus value for a label of CASE
statement.
*4: To find the locations where CASE statements are used, open multiple STs in Multi-Language Editor and search for CASE.

n Enhanced Checking by Integrity Analyzer
l Checking for Multiple Writing to the Same Variable

Multiple writing to the same variable can reduce the program readability and end up downloading
of programs that cause unintended behavior. Integrity Analyzer in R2.02 detects multiple writing
to the same variable and displays a warning message.
This warning message is not output with the revisions before R2.02, but it will be displayed
after you have upgraded to R2.02 when the program contains any multiple writing to the same
variable. If this warning message is displayed, examine the program to find out if you can
eliminate the multiple writing. If you find that the multiple writing is necessary, acknowledge
the results of analysis in Integrity Analyzer and you can download the program to SCS without
change. In this case, the program can be used as a function allowed for safety application after
verifying its validity in user tests.
l Checking for Multiple Calls to the Same FB Instance

Multiple calls to the same function block (FB) instance can lead to an unexpected state in the
system and the program may not behave as intended. Integrity Analyzer in R2.02 detects
multiple calls to the same FB instance and displays a warning message.
This warning message is not output with the revisions before R2.02, but it will be displayed after
you have upgraded to R2.02 when the program contains multiple calls to the same FB instance.
If this warning message is displayed, examine the program to find out if you can eliminate the
multiple calls. If you find that the multiple calls are necessary, acknowledge the results of analysis
in Integrity Analyzer and you can download the program to SCS without change. In this case, the
program can be used as a function allowed for safety application after verifying its validity in user
tests.
l Checking for Writing to Output Variable Status

I/O variable statuses (.status) are the data that reflect the actual statuses (normal/abnormal) of
I/O channels. Therefore, they should not be changed by user logic. Integrity Analyzer in R2.02
detects writing to output variable statuses and raises an error.
In revisions before R2.02, no such error is raised. But this error will be raised after you have
upgraded to R2.02 when there is any program that writes to any output variable status. If an error
message is displayed, change the program to eliminate the writing to output variable statuses.

9.6.2 Compatibility with Earlier Revisions
n Behavior of AIO/DIO Modules at Online Change Download

When online change downloading is performed after you have changed any settings of I/O
Parameter Builder that require downloading to I/O modules (IOM download), the target AIO/DIO
modules continue operation if the SCS system program revision is R2.02 or later while the AIO/
DIO modules are stopped with revisions earlier than R2.02.
This section explains the behaviors of AIO/DIO modules when the SCS system program revision
is earlier than R2.02.
SEE
ALSO For the setting items that require IOM download, see the following sections of the Safety Control Station
Reference (IM 32S03B10-21E):
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 Behavior of Input Modules

At the time of online change, the data status of all channels of the target module become
BAD, and the diagnostic information message IOM Fail appears. The input signals of all
channels of the module are processed according to the [Input Processing at Fault] settings.
If on-demand HART communication with PRM is performed, the HART communication is
discontinued during the IOM Fail status.
On completion of online change download, the channels data automatically return to the
values input to the channels and all data statuses become GOOD.
A diagnostic information message indicating that the input module has recovered to normal
is output.
For dual-redundantly configured I/O modules, the odd-numbered module takes the control
right.
TIP
If any setting items that require IOM download and the setting of [Input Processing at Fault] or [Input Value
at Fault] are changed online simultaneously, the input value will conform to the changed settings of [Input
Processing at Fault] and [Input Value at Fault].

l Behavior of Output Modules
At the time of online change, the data status of all channels of the target module become9.7
BAD, and the diagnostic information message IOM Fail appears. The output values on all
channels change to 0 if the target module is a discrete output module, and change to the
tight-shut output values(*1) if the target module is an analog output module.
If on-demand HART communication with PRM is performed, the HART communication is
discontinued during the IOM Fail status.
On completion of online change download, the data status of all channels become GOOD,
while the output values still remain 0 with a discrete output module or remain the tight-shut
output values with an analog output module.
A diagnostic information message indicating that the output module has recovered to normal
is output.
For dual-redundantly configured output modules, the odd-numbered module takes the
control right.
If the user performs the output enable operation, outputs of the application logic are output
from the output module.
*1: A tight-shut output value can be set for each channel using the I/O Parameter Builder.
n Changes in Multi-Language Editor Specifications
l Font and Font Color are Set for Each Project

In revisions earlier than R2.02, the font and font color shown in the function block diagram (FBD)
window of Multi-Language Editor are retained for each user of the computer.
From R2.02, the font and font color settings for FBD windows are retained for each project. When
a project is first opened in R2.02, the font and font color settings used by the user who opened
the project will be retained in the project.
l FBD Guidelines are Set for Each Project

In revisions earlier than R2.02, the guideline setting for the FBD window of Multi-Language Editor
is retained for each computer.
From R2.02, the guideline setting is retained for each project. The guideline setting when the
project is first opened in R2.02 will be retained in the project.


In this section, the cautionary notes for upgrading from R2.02 to R2.03 are explained.
Before you upgrade, also read the cautionary notes for the previous revisions issued after
IMPORTANT
When integrating ProSafe-RS and CENTUM VP, the newly added features of ProSafe-RS
R2.03 are fully supported in CENTUM VP R4.02 and later versions.
PRM of the versions earlier than R3.04 do not support the SCSP2 stations that were added
in ProSafe-RS R2.03.
See
ALSO For the behaviors of CENTUM that are related to the new features of ProSafe-RS R2.03 when ProSafe-RS is
integrated with CENTUM VP earlier than R4.02 or CS 3000, see the following:
Appendix. Limitations for Each Software Release Number of CENTUM of the Integration with CENTUM
VP/CS 3000 (IM 32S01E10-21E)

l Control Bus Drivers

The control bus drivers installed on the PC should be upgraded to the version supplied in R2.03.

In order to use the features added or modified in R2.03, install the R2.03 or later software and
open the existing SCS project.
SEE
ALSO For cautionary notes for opening an existing SCS project, see the following:

9.7.1 Cautionary Notes for Upgrading
n Procedure for Using New and Modified Features

After the SENG software has been upgraded to R2.03, some of the features added or modified in
the R2.03 require further steps, such as off-line downloading to SCS, before they can be used. In
the following, the steps are explained for each feature.
SEE
ALSO For Procedure B through Procedure F mentioned in this section, see the following in Setup Procedures
after Upgrading Software in 6.5, Setups after Upgrading ProSafe-RS Software:
l Procedure D: Setting Definition Items for New Features and Off-line Download
l Procedure E: Clean Project, Build, and Off-line Download
l Procedure F: Setting Definition Items for New Features, Clean Project, Build, and Off-line Download
l New I/O Module (SDV53A)

To use the I/O module SDV53A newly supported in R2.03, you need to perform Procedure C.
l New Function Blocks in R2.03

To use the new FBs in R2.03, such as SYS_SCANEXT (scan period extension indicator), you
need to perform Procedure C on an SENG of R2.03 or later.
l Online Change Download

From R2.03, the following changes can be made by online change download.
Change the scan period
Add or delete input/output modules
Rename POUs
Change the type and attributes of FB instances
Change the definitions on SCS Constants Builder
To download these changes online, you need to perform Procedure E on an SENG of R2.03 or
later.
SEE
ALSO For information about online changes to SCS with R2.02 or earlier system program, see the following:
n Online Changeable Information in 9.7.2, Compatibility with Earlier Revisions
l Inter-SCS Safety Communication Locking Functions

To use the functions for locking inter-SCS safety communication, you need to perform
Procedure E on an SENG of R2.03 or later. However, if you also want to use the new system
FB of SYS_FORCE_EB (inter-SCS safety communication forcing status management), you
need to perform Procedure C.

l Automatic IOM Download
To use automatic IOM download, you need to perform Procedure F on an SENG of R2.03 or
later. Use the SCS Constants Builder and set so as to enable the automatic IOM download.
l Automatic Scan Period Extension under High CPU Load

To use automatic scan period extension, you need to perform Procedure F on an SENG of
R2.03 or later. Use the SCS Constants Builder and set [Extend scan period automatically] to
Yes. However, if you also want to use the new system FB of SYS_SCANEXT (scan period
extension indicator), you need to perform Procedure C.
IMPORTANT
If you use automatic scan period extension in a system that does not include SCS Maintenance
Support Tool on SENG or CENTUM HIS, you must perform Procedure C on an SENG of R2.03
or later. This is because, in such a system, you need to use the SYS_SCANEXT FB (scan period
extension indicator) to detect whether the SCS is running with an automatically-extended scan
period.
l Specifying Behavior at Abnormal Calculation

To enable specification of the SCS behavior at abnormal calculation, you need to perform
Procedure F on an SENG of R2.03 or later. Use the SCS Constants Builder and specify the
behavior of the SCS at abnormal calculation. However, if you also want to use the new system
FB of SYS_CERR (computation error indicator), you need to perform Procedure C.
IMPORTANT
If you want to specify the behavior of the SCS at abnormal calculation in a system that does
not include SCS Maintenance Support Tool on SENG or CENTUM HIS, you must perform
Procedure C on an SENG of R2.03 or later. This is because, in such a system, you need to use
the SYS_CERR FB (computation error indicator) to detect that the SCS is running even after
abnormal calculation has occurred.
l Improvement in SCS Software Performance

To improve the software performance of SCSP1 or SCSV, you need to perform Procedure B on
an SENG of R2.03 or later.
n Cautionary Note on Off-line Download after Upgrading to R2.03

If you try to off-line download an existing project immediately after upgrading the ProSafe-RS
software to R2.03, an error occurs. You need to run Clean Project and Build before off-line
downloading the project.

9.7.2 Compatibility with Earlier Revisions

This section describes the specifications and cautionary notes of SCS with a system
program before R2.03 that are critical to safety as the information on compatibility. Read
this section when you use SCS with a system program before R2.03.
n Inter-SCS Safety Communication

The Inter-SCS Communication Lock Window is not available.
For testing of inter-SCS safety communication and maintenance, internal variables should be
connected to the OUT of consumer inter-SCS safety communication FBs and the application
should read the values of these internal variables. During testing and maintenance, you need to
lock the connected variables as necessary.
n Online Changeable Information

The online changeable information in SCS with a system program before R2.03 is as follows.
l POU Information that is Changeable On-line

Table POU Information
On-line Change
Modification
Program User-Defined FB User-Defined FU
Adding/deleting variables Yes Yes (*1) Yes (*4)
Adding a variable to be named the same as that of
No No No
a deleted variable
Changing attributes of variables No No No
Adding/deleting I/O variables Yes - -
Adding/deleting FU Yes Yes Yes
Adding/deleting user-defined FU (*3) Yes Yes Yes
Adding/deleting FB instances Yes No -
Adding/deleting user-defined FB (*3) Yes No -
Adding a FB to be named the same Instance as
No - -
that of a deleted FB
Changing logic Yes Yes (*1) Yes (*1)
Creating/deleting programs
No (*2)
Changing program names
Creating/deleting user-defined Function Blocks
No (*2)
Changing user-defined Function Block names
Creating/deleting user-defined Functions
No (*2)
Changing user-defined Function names
Yes: Changeable by on-line change download.
No: Off-line download is required.
*1: It is not allowed to increase/decrease parameter values or change attributes. They cause an error when the database is
downloaded.
*2: An error occurs during downloading.
*3: When user-defined FU/FB are added, they need to be tested. Pre-validated user-defined FU/FB do not need to be tested.
*4: On-line change is only possible for local variables.

l I/O Module Information that is Changeable On-line
Table I/O Module Information
Modification On-line Change
Adding nodes No
Deleting nodes No
Changing parameters of nodes Yes
Adding I/O modules No
Deleting I/O modules No
Changing redundant I/O modules No
Changing parameters of I/O modules Yes
Changing parameters of channels Yes
Changing subsystem communication definitions Yes
Defining link between a variable and an idle channel Yes
Deleting link between a channel and a variable Yes
Changing link between a channel and a variable Yes
Adding, changing or deleting subsystem communication definitions Yes
Changing wiring of communication input/output FBs Yes
l Constants and Network Information that are Changeable On-line

Table Constants and Network
Classification Modification On-line Change
Name No
Configuration
Password No (*1)
Name No
Resource Number No
Resource Scan period No

Number of variables permitted for online
No
maintenance
Size of temporary variables and constants area No
IP address No
Network Station address No
Inter-SCS safety Communication (Binding) No
With or without optional ESB bus repeater No
Optional ESB BUS Repeater
Max. extension distance No
*1: Setting and changing passwords is ignored.

l Builder Definitions that are Changeable On-line
Table On-line Change Download
Builders On-line Change
SCS Constants Builder No
I/O Parameter Builder Yes
Communication I/O Builder Yes
SCS Link Transmission Builder Yes
Modbus Address Builder Yes
Tag Name Builder Yes
Alarm Priority Builder No
Alarm Processing Table Builder No
n Behaviors at Abnormal Calculation in Application Logic

If abnormal calculation occurs in the application logic of an SCS with a system program before
R2.03, the SCS stops.
l About Behaviors of SCS at Abnormal Calculation

If an overflow or division by zero occurs in operations with REAL-type variables, or division
by zero in operations with integer-type variables, SCS stops.
When floating-point data is converted to a DINT number by the ANY_TO_DINT function, if
the resultant number exceeds the maximum or falls below the minimum integer values (i.e.
overflow occurs), the SCS stops.
For the input to ANY_TO_TIME, use a DINT type value in the range from 0 to 86400000.
If a value beyond this range is used, it cannot return a proper time. Note that when a real
number value greater than 4294967295 (the maximum number of the unsigned 32-bit
integer) or smaller than -2147483648 (the minimum number of the unsigned 32-bit integer)
is used, the SCS stops.
If access to the outside of an array occurs, the SCS stops.

<10. Installing the Common Functions of ProSafe-RS Software> 10-1
10. Installing the Common Functions of

ProSafe-RS Software
Installing the common functions of ProSafe-RS software is required when you need
to install the functions those act collaboratively with CENTUM systems. Installing the
common functions does not require the license of ProSafe-RS as long as any one of the
CENTUM packages has been installed in the PC.
The common functions of ProSafe-RS software are the software group that consists
of programs, libraries and data files shared by all the ProSafe-RS applications. SCS
Simulator is one of them. The common functions of ProSafe-RS software are installed
when at least one ProSafe-RS package is installed to the PC.
In this chapter, how to install the common functions of ProSafe-RS software to the PC
where no other ProSafe-RS package is installed will be explained.
n Installing the Common Functions of ProSafe-RS Software Only

On a PC installed with any CENTUM package, you can install the common functions of ProSafe-
RS software without the license of ProSafe-RS package (No need for key-code FD) to the PC.
By using the CENTUM packages shown in the following table in combination with the common
functions of ProSafe-RS, you can use functions such as SCS Simulator.
Table CENTUM Packages Used with the Common Functions of ProSafe-RS Software
Model CENTUM VP Package CS 3000 Package
LPC6920 SOE Viewer Package SOE Viewer Package
LHS5420 Test Function Test Function
LHS5426 FCS Simulator Package FCS Simulator Package
LHM5150 Test Function (for CENTUM VP Small) Test Function (for CS 3000 Small)

n New Installation of the Common Functions of ProSafe-RS Software

How to install the common functions of ProSafe-RS software to a PC where ProSafe-RS is not
installed will be explained below.
Relevant CENTUM packages must be installed before installing the common functions of
l Items to be Prepared at New Installation

Prepare the following items before a new installation of the common functions of ProSafe-RS
software.
l Preparation before New Installation of the Common Functions of ProSafe-RS

Software
Carry out the following tasks before starting the installer.
TIP
Restart the PC after installing the common functions of ProSafe-RS software.
l Procedure of New Installation of the Common Functions of ProSafe-RS
IMPORTANT
If the Microsoft .NET Framework 3.5 SP1 and Microsoft Visual C++ 2008 Redistributable are
not installed in the PC, a dialog box that prompts you to install them appears after you start the
version upgrade installation. Be sure to install them.
1. Logon as an administrative user. In domain environment, the domain user for ProSafe-RS
installation user account should be used.
3. Insert the ProSafe-RS CD-ROM into the CD-ROM drive. There is no need for a keycode
FD.

100001E.ai
Figure Setup Requirements Dialog Box
5. When installation of Microsoft .NET Framework and Microsoft Visual C++ 2008
Redistributable is completed, Welcome window will be displayed.
6. Click the [Next] button in the Welcome dialog box. The user information entered when
installing CENTUM will be displayed in a dialog box.
7. Edit the user name and department, if necessary, and then click [Next] to continue.
The ID Number dialog box appears.
8. Check the ID number (ID number of the CENTUM package), and then click [Next].
Then Common Functions is displayed in the package list.
Package List
Common Functions
Install to:
F:\Program Files\ProSafe-RS\
Change...
InstallShield
Help Space < Back Next > Cancel
100003E.ai
9. Click the [NEXT] button in the Package List Dialog Box.


installation.
12. Remove the CD-ROM from drive and click the [Yes] button in the dialog box to restart the
PC. Click the [No] button to restart the PC later.
IMPORTANT
Installed common functions of ProSafe-RS does not operate properly until the PC is restarted
after installing the common functions of ProSafe-RS software.
n Add Other ProSafe-RS Packages

The procedure for installing additional ProSafe-RS packages to the PC installed with the
common functions of ProSafe-RS software without revision upgrade is the same as that for
adding a package to the PC installed with ProSafe-RS.
SEE
ALSO For more information about addition of ProSafe-RS software packages without revision upgrade, see the
following:
5.1, Addition of ProSafe-RS Software Packages (without Revision Upgrade)
n Reinstallation of the Common Functions of ProSafe-RS Software

How to reinstall the ProSafe-RS common function software on a PC where the ProSafe-RS
common function software has already been installed will be explained. It may for instance be
necessary to reinstall the software if you accidentally deleted part of the common functions of
ProSafe-RS software or in other similar situations.
Install relevant CENTUM packages again if necessary.
SEE
ALSO Information about reinstalling the common functions of ProSafe-RS, due to the same as for reinstalling the
ProSafe-RS software, see the following:
5.2, Reinstallation of the ProSafe-RS Software

n Revision Upgrade of the Common Functions of ProSafe-RS Software

(without Other Package of ProSafe-RS Addition)
How to upgrade the common functions of ProSafe-RS software without adding other ProSafe-RS
Packages to the PC where the common functions of ProSafe-RS software have been already
installed will be explained.
Also upgrade relevant CENTUM packages if necessary.
l Items to be Prepared at Revision Upgrade of the Common Functions of

ProSafe-RS Software
Prepare the following items before a revision upgrade of the common functions of ProSafe-RS
software.
l Preparation Before Revision Upgrade of the Common Functions of ProSafe-

RS Software
Carry out the following tasks before starting the revision upgrade.
TIP
Restart the PC after upgrading the common functions of ProSafe-RS software revision.

l Procedure of Revision Upgrade of the Common Functions of ProSafe-RS
Software
logon the PC.
3. Insert the ProSafe-RS CD-ROM into the CD-ROM drive. There is no need for a keycode
FD.
5. The Welcome dialog box appears. Click the [Next] button. The Customer Information
dialog box appears.
TIP
Yes No
100005E.ai
7. Check the ID number (ID number of the CENTUM package), and then click [Next] .
Then Common Functions is displayed in the package list.
Package List
Common Functions
Install to:
F:\Program Files\ProSafe-RS\
Change...
InstallShield
Help Space < Back Next > Cancel
100004E.ai

8. Click the [Next] button in the Package List Dialog Box.
9. Click the [Install] button to start the installation.
11. Remove the CD-ROM from drive and click the [Yes] button in the dialog box to restart the
PC. Click the [No] button to restart the PC later.
IMPORTANT
Installed common functions of ProSafe-RS does not operate properly until the PC is restarted
after installing the common functions of ProSafe-RS software.
n Revision Upgrade of the Common Functions of ProSafe-RS Software

(with ProSafe-RS other Package Addition)
The procedure for upgrading the common functions of ProSafe-RS software with installing
additional ProSafe-RS Packages to the PC is the same as that for upgrading the software of PC
installed with ProSafe-RS.
Also upgrade the relevant CENTUM packages if necessary.
SEE
ALSO Since the information about reinstalling the common function of ProSafe-RS software is the same as revision
upgrade of the ProSafe-RS software with package addition, see the following:

<10.1 Installing SCS Simulator> 10-8
10.1 Installing SCS Simulator

To run the SCS Simulator, any one of the CENTUM packages should be installed
beforehand and then the common functions of ProSafe-RS sotfware should be installed.
For installing the common functions of ProSafe-RS software, the license (key-code FD) is
not required.
Table CENTUM Packages for SCS Simulator

Model CENTUM VP Package CS 3000 Package
LHS5420 Test Function Test Function
LHS5426 FCS Simulator Package FCS Simulator Package
LHM5150 Test Function (for CENTUM VP Small) Test Function (for CS 3000 Small)
SEE
ALSO For more information about installing CENTUM packages (LHS5420/LHS5426/LHM5150), see the following:
CS 3000 Installation (IM 33Q01C10-01E)
CENTUM VP Installation (IM 33M01A20-40E)

<10.2 Installation for Integration with CENTUM SOE Viewer> 10-9
10.2 Installation for Integration with CENTUM

SOE Viewer
When ProSafe-RS is integrated with CENTUM, the SCS sequence of events (SOE) can
be viewed on CENTUM SOE Viewer. This is referred to as Integration with CENTUM
SOE Viewer. In this chapter, the procedure of the installation for the integration will be
explained.
Integration with CENTUM SOE Viewer can be realized by installing CENTUM SOE Viewer
package (LPC6920, license required) and then common functions of ProSafe-RS software
(license not required) to a PC.
n Installation Procedure
Installation procedure is as follows.
Start
Install CENTUM
SOE Viewer
Install ProSafe-RS
common functions
(license not required)
END
100201E.ai
Figure Installation Procedure
n Cautions
The following cautions need to be noted during installation.
After installing CENTUM SOE Viewer package (LPC6920), install the common functions of
The common functions of ProSafe-RS software can be installed without keycode. Therefore
the keycode FD is not required for the installation.
SEE
ALSO For more information about installing CENTUM SOE Viewer package (LPC6920), see the following:
CS 3000 Installation (IM 33Q01C10-01E)
CENTUM VP Installation (IM 33M01A20-40E)
For viewing SOE of SCS on CENTUM SOE Viewer, it is necessary to connect the PC and SCS
via V net or Vnet/IP.

Blank Page
<11. Security Setting Utility> 11-1
11. Security Setting Utility

The PC hardening of ProSafe-RS is performed with Security Setting Utility. When
installing the ProSafe-RS software (including the Common functions of ProSafe-RS) is
completed, the Security Setting Utility will be started automatically. However, the Security
Setting Utility can be started at anytime for defining securities.
n Timing of Setting Securities

The PC hardening can be performed at the following timings.
l Timing of New Installation

When running a new installation, the Security Setting Utility will be automatically started at the
last part of the installation. The security settings can be completed by following the instructions on
the dialog boxes to select a proper security model of security settings. The security settings must
be performed on each new installation.
l Anytime
For setting the IT securities, the Security Setting Utility in the ProSafe-RS CD-ROM can be
started at anytime.
IMPORTANT
The security settings should be performed by the same administrative user that installed the
Once the security settings has been completed, the next installation should be performed by
the same administrative user who performed the previous security settings.
Before you perform the security settings for the PC in Windows domain environment, the
following items must be confirmed:
On the domain controller, an administrative user account for installing ProSafe-RS software
has been created.
On the domain controller, the ProSafe-RS user groups have been created.
The user who performs the installation needs to be registered to Domain Admins user group
and PSF_MAINTENANCE user group.
l How to Start the Security Setting Utility at Anytime

1. Logon to the administrative user account that installed ProSafe-RS software.
2. Terminate all the running applications.
3. Start RHCSecurityUtility.exe (Security Setting Utility) under the SECURITY folder in the
CD-ROM .
Example (Suppose the CD-ROM drive is D.):
D:\SECURITY\RHCSecurityUtility.exe
When executing this program in Windows Vista environment, after starting it, a User
Account Control dialog box may be displayed. You need to click [Continue] on this dialog
box.
4. The Security Setting Utility will be started.

n Operation of the Security Setting Utility

How to use the Security Setting Utility will be explained as follows:
1. After starting the Security Setting Utility, a dialog box will be displayed as follows. Click
[Next] to continue.
110001E.ai
Figure Security Setting Utility (Welcome Page)
2. A dialog box for selection security type will be displayed. Check the proper type and then
click [Next].
110002E.ai
Figure Select Security Type

3. The security settings contain three categories. Choose one or two for the PC is possible.
However, it is recommended to check all the categories. If one category is not checked, the
existing security settings of that category in the PC will be retained.
Click [Next] to start the security setting.
110003E.ai
Figure Security Setting Categories
4. When the security setting is completed, the dialog box will be displayed as follows. Click
[Finish] and restart the PC.
110004E.ai
Figure Security Setting Finished

IMPORTANT
If the security setting fails, restart the PC and perform the security setting again.
n When Changing Security Type

If you want to change the type of the security setting after the security setting is completed,
you need to redefine the proper security setting type or category on Security Setting Utility and
perform the setting again.
The procedure for switching two types of standard model of security settings is explained below.
l Switch from Stand alone Management to Windows Domain Management

In the PC that already designated with stand alone management type security settings, in order
to switch to the domain management type, the procedure below should be followed. Moreover,
the users and user groups must be created on the domain controller PC that handles the
ProSafe-RS beforehand.
1. Logon to a user account that belongs to the local user group of PSF_MAINTENANCE.
2. Insert the ProSafe-RS installation media to the CD-ROM drive and then start the Security
Setting Utility.
3. Choose [Set the security the same as ProSafe-RS R1. (Legacy model)] and complete the
security settings.
4. Restart the PC.
5. Add the PC as a member of a Windows domain and then restart the PC.
6. Use a user that belongs to the PSF_MAINTENANCE group of the domain to logon.
Setting Utility.
8. Choose [Domain: Set the security for domain account. (Standard model)] and complete the
security settings.
9. Restart the PC.
l Switch from Windows Domain Management to Stand alone Management

1. Logon to a user account that belongs to the local PC user group of PSF_MAINTENANCE_
LCL.
2. Remove the PC from the Windows domain and then restart the PC.
3. Logon the PC with the same user account of step 1.
Setting Utility.
5. Choose [Stand alone: Set the security for local account. (Standard model)] and complete
the security settings.
6. Restart the PC.

<12. Setting of Windows Domain Environment> 12-1
12. Setting of Windows Domain

Environment
If the ProSafe-RS user accounts are controlled by Windows domain controller, the domain
environment needs to be defined on the Windows Server before installing the ProSafe-RS
software.
How to configure the domain environment for ProSafe-RS will be explained below.
Procedure for Adding a User and Group.
Procedure for Adding a Client PC to a Domain
The details of constructing a domain controller and the system settings of Windows
server will not be explained in this document. Please refer the related Windows
documentation
n Domain Environment Setup Procedure

The domain environment required for ProSafe-RS can be setup by following steps.
1. Configuring domain controller.
2. Create domain user accounts.
3. Create domain groups (In case the standard model of PC hardening is used)
4. Add the domain users to as the members of the domain group (In case the standard model
of PC hardening is used)
5. Add the client PC to the domain.

n Create Domain User Accounts

In this section, how to create the domain user accounts in Windows server after configuring the
domain controller will be explained.
l Required User Accounts for Operating ProSafe-RS

For operating ProSafe-RS, the following user accounts are required. These accounts need to be
created respectively.
Administrative User
An administrative user account needs to be created for installing ProSafe-RS.
IMPORTANT
The administrative user account for installing ProSafe-RS must be created before installing the
ProSafe-RS.
Required User Accounts for Maintaining ProSafe-RS

For maintaining ProSafe-RS, various user accounts corresponding to various privileges
need to be created.
Examples : Engineer, account, Maintenance personnel account and network administrator
account.
IMPORTANT
When standard model of PC hardening is used, the user accounts corresponding to each role
must be created. After applying the standard model of PC hardening, user groups corresponding
to each role will be created. The access permission and restrictions will be applied by each user
group.

l Procedure of Creating User Accounts
1. Logon the domain controller server PC using Administrator account.
2. Choose [All Programs]-[Administrative Tools]-[Active Directory Users and Computers] from
Start menu.
3. Choose [Users] folder from the tree view in the left pane.
120001E.ai
Figure Active Directory Users and Computers
4. Right click [Users] folder on the tree view and choose [New]-[Users] from the menu.

5. When the following window displays, enter the required items and then click [Next]. The
following items are not omissible.
Full name
User logon name
120002E.ai
Figure Entries for User
6. Enter a [Password] and check the required options. Click [Next] to continue.
120003E.ai
Figure Password Setting

7. Click [Finish].
120004E.ai
Figure Entries for User Finished
8. Open [Users] folder and make sure that the new domain user is already added in the list.
120005E.ai
Figure New Domain User Confirmation

n Procedure of Creating Domain Groups

When the standard model of information security settings is used, the domain user groups need
to be created after creating the user accounts. When the legacy model of PC hardening is used,
this procedure is not needed.
l Required User Groups for Operating ProSafe-RS

For operating ProSafe-RS, the following user groups need to be created on the domain
controller.
IMPORTANT
When the standard model of PC hardening is used, the following user groups must be created:
PSF_OPERATOR
PSF_ENGINEER
PSF_OPC
PSF_MAINTENANCE
PSF_UTL

l Procedure of Creating User Groups
1. Logon the domain controller server PC using Administrator account.
2. Choose [All Programs]-[Administrative Tools]-[Active Directory Users and Computers] from
Start menu.
3. Choose [Users] folder from the tree view in the left pane and then choose [New]-[Group]
from the menu.
120006E.ai
Figure Choose Group

4. When the following dialog box displays, enter the following items and then click [OK].
Group name: Enter a group name
Group scope: Select according to management policy.
Group type: Security
120007E.ai
Figure Entries for User Groups
5. Open the [Users] folder and make sure the new groups are added.
120008E.ai
Figure New User Group Confirmation

n Add Domain Users to Domain Groups

When standard model of PC hardening is applied, the domain users need to be added to the
domain groups. For legacy model of PC hardening, this is not required.
l Settings for the User who executes the Installation of ProSafe-RS Software
Before installing the ProSafe-RS software, the following setting needs to be performed.
IMPORTANT
The user who executes ProSafe-RS installation needs to be registered to Domain Admins user
group and PSF_MAINTENANCE user group.
Procedure for Adding Domain Users to Domain Groups

This section describes an example of adding a domain user to PSF_MAINTENANCE group.
1. Double click a user to be defined.
120018E.ai
Figure Select a User

2. When the properties sheet of the selected user is displayed, open [Member Of] tab.
120019E.ai
Figure [Member Of] Tab
3. Click [Add], [Select Groups] dialog box will be displayed.
120020E.ai
Figure Select Groups

4. Click [Advanced] and the detailed window of [Select Groups] will be displayed.
120021E.ai
Figure Select Groups (Advanced)
5. Click [Find Now] to display groups, and for example, select [PSF_MAINTENANCE] group
and click [OK].
120022E.ai
Figure Select Group

6. On the displayed dialog box, make sure that PSF_MAINTENANCE is designated, then click
[OK].
120023E.ai
Figure Confirm the Group
7. On the displayed dialog box make sure that the PSF_MAINTENANCE is designated, then
click [OK].
120024E.ai
Figure Display of the Group Designated to the User

Set Administrative Privileges
This section describes how to assign administrative privileges to a domain user.
1. Add the domain user to the Domain Admins group.
2. Open the Properties dialog box for the user. Click the Member Of tab, select [Domain
Admins], and click the [Set Primary Group] button. Primary group of the user changes to
Domain Admins.
120025E.ai
Figure Properties Sheet of a User

3. Choose [Domain Users] and then click [Remove].
120026E.ai
Figure Remove Domain Users
4. Confirm that [Domain Users] is removed and then click [OK].
120027E.ai
Figure Properties of the User with Administrator Privileges

n Add a Client PC to the Domain

On the domain controller, after the preparation of domain users and domain user groups, the
client PC needs to be added to the domain. The procedure for adding a client PC to the domain
is different when performing on domain controller and on client. The procedure for adding a PC to
the domain by client side will be explained respectively by Windows OS type.
l How to add a Client PC to Domain (Windows Vista)

For the PC of Windows Vista, use the following procedure to add the client to the domain.
1. Choose [Computer] from Start menu.
2. When the following dialog box displays, click [System Properties].
120009E.ai
Figure Computer

3. When the following dialog box displays, click [Advanced system settings].
120010E.ai
Figure Advanced System Settings
4. Choose [Computer Name] tab on System Properties dialog box, and then click [Change].
120011E.ai

5. On [Computer Name/Domain Changes] dialog box, choose[Domain] and then enter a
domain name and click [OK].
120012E.ai
Figure Computer Name/Domain Changes
6. On the displayed dialog box, enter items to [Computer name] and [Password] for the
account added to as a domain member and permitted to access the domain, then click [OK].
7. On the confirmation dialog box for the changes, click [OK] to continue. .
8. Click [Restart Now] on the confirmation dialog box to restart the PC.

l How to Add a Client PC to Domain from Client PC(Windows XP)
For the PC of Windows XP, use the following procedure to add the client to the domain.
1. Right click [My Computer] on Start menu and then choose [Properties] from the menu.
2. On the following window, choose [Computer Name] tab, and then click [Change].
120014E.ai

3. When the following window displays, choose [Domain] and enter a domain name and then
click [OK].
120015E.ai
Figure Computer Name Changes
4. On the displayed dialog box, enter items for [User name] and [Password] for the account
added to as a domain member and permitted to access the domain and then click [OK].
5. On the confirmation dialog box for the changes, click [OK] to continue.
6. Click [Restart Now] on the dialog box prompting for restarting the PC so as to restart the PC.

l Make Sure the Client PC is Added to the Domain
1. Logon the domain controller PC using the Administrator account, and then start [Active
Directory Users and Computers].
2. Make sure that the added PC is displayed in the [Computers] folder.
120017E.ai
Figure Users and Computers
n Notices when Using in Domain Environment

Notices when using ProSafe-RS in domain environment will be explained below.
l Notice on Installing SOE OPC Interface Package

Notice on installing SOE OPC Interface package to the PC in domain environment are as follows:
Windows Server is generally used for configuring the domain environment. The default
password of the EXAUSER user created during installation may conflict with the password
policy of Windows Server. So, the user cannot be registered. Consequently, connection with the
supervisory computers via OPC will fail.
To avoid this problem, it is necessary to temporarily disable the password policy of [Password
must meet complexity requirements] on Windows Server. And then enable it after installing the
SOE OPC interface package and completing the setups through the SOE OPC interface.

Rev-1
Revision Information
Title : Installation
Manual No. : IM 32S01C50-21E
Dec. 2009/3rd Edition/R2.03 or later*

* : Denotes the release number of the software corresponding to the contents of this users manual. The
revised contents are valid until the next edition is issued.
Overall Revised for the support of Windows Server 2008 and addition of SCSP2, VF702, and VI702.
1.1 Changed hardware operation environment.
Changed Table: Correspondence between ProSafe-RS Software Release Numbers and Windows
OS Versions,
Table: List of Software that can Coexist with ProSafe-RS, and
Table: Correspondence between ProSafe-RS and CS 3000 Release Numbers.
2.1 Added SCP461.
2.2 Added VF702.
3. Improved descriptions and corrected errors.
3.2 Changed the procedures for installing the control bus driver.
3.4 Changed the procedures for installing/updating/deleting the open communication driver
4.1 Changed the procedures for installing ProSafe-RS software.
4.2 Added n Settings for the Case When SOE OPC Interface Package and CENTUM VP Exaopc OPC
Interface Package are Installed in the Same PC.
4.4 Changed description about Adobe Reader.
6. Changed the procedures for updating the control bus driver and ProSafe-RS software.
6.5 Added Procedure E and Procedure F.
7. Changed the procedures for deleting the control bus driver.
9.7 Newly added.
10. Changed the procedures for installing/updating the ProSafe-RS common functions.
Changed the requirements for installation.
Dec. 2008/2nd Edition/R2.02 or later

Overall CS 3000 was changed to CENTUM, which refers to both CENTUM VP and CS 3000.
1. Figure Flow of Installation Tasks was modified.
1.1 Table Correspondence between ProSafe-RS Software Release Numbers and Windows OS
Versions was changed.
Table List of Software that can Coexist with ProSafe-RS was changed.
Table Correspondence between ProSafe-RS and CS 3000 Release Numbers was changed.
2. Descriptions of Ethernet card were changed.
Section 2.2.1 in the previous edition was removed.
2.1 Figure of SCP451 processor module was added.
3. Information provided in the supplement was included.
Descriptions of operation procedures were simplified.
3.1 Description of Ethernet driver installation was removed.
3.3 Description of DNS server address setting was changed.
3.4 Description of DNS server address setting was changed.
4.1 Description about the installer provided in the Release Information IM was added.
4.4 Description was modified for Adobe Reader 9.0.0.
5. n Notes on Installation was added.
6. n Notes on Installation was added.
6.1 Information provided in the supplement was included.
Descriptions of operation procedures were simplified.
6.5 A cautionary note was added to l Procedure A: Opening SCS Projects.
7. n Note on Network Connection was added.
7.1 Descriptions of operation procedures were simplified.
9. Chapter title was changed
9.5 Information provided in the supplement was included.
9.6 Newly added.
10. Table CENTUM Packages Used with the Common Functions of ProSafe-RS Software was
changed.
10.1 Table CENTUM Packages for SCS Simulator was changed.
12. Information provided in the supplement was included.

Rev-2
May 2008/1st Edition/R2.01 or later
Newly published.
n For Questions and More Information

Online Query: A query form is available on the following URL for online query.
http://www.yokogawa.com/iss/
If you want more information about Yokogawa products, you can visit
Yokogawas homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by Process Automation Product Marketing Dept.
Industrial Automation Systems Business Div.
Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

S01C5021 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S01C5021 PDF

Uploaded by

Copyright:

Available Formats

Users

Chapter 1: How to Read this Manual

ProSafe-RS Document Map

Safety Control Station Integration with Open Interfaces

Engineering Utilities and Messages

IM 32S01C50-21E 2nd Edition : Dec.15,2008-00

Indicates that main switch is ON.

Indicates that main switch is OFF.

IM 32S01C50-21E 1st Edition : May 30,2008-00

n Notes on Handling User Manuals

n Warning and Disclaimer

IM 32S01C50-21E 1st Edition : May 30,2008-00

l Commonly used Conventions throughout User manuals:

Character strings in the following font and style:

Character string enclosed by brackets ({ }):

l Conventions used to show Key or Button Operations:

Characters enclosed by square brackets ([ ]):

l Conventions of User Defined Folder

IM 32S01C50-21E 2nd Edition : Dec.15,2008-00

Indicates a source to be referred to.

n Integration with CENTUM

IM 32S01C50-21E 2nd Edition : Dec.15,2008-00

n About Explanation of System Behavior

n About Station Types

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

Copyright and Trademark Notices

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

1. How to Read this Manual

Chapter that must be read Chapters to be read as necessary

Figure How to Read this Manual

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

n Overall Flow of New Installation Tasks

1. SCS hardware setup See 2, Confirmation of Hardware Setup

This task is not required if Windows has already

3. Windows Service This task is not required if Windows Service Pack

4. Windows setup See 3.1, Windows Setup.

6. Installing V net interface card

7. Network setup See 3.3, Windows Network Setup

10. Setup Information Securities See 11, Security Setting Utility

11. Electronic document setting See 4.2, Online Manual Setting

12. Settings after ProSafe-RS

Create User Accounts

Figure Flow of Installation Tasks

IM 32S01C50-21E 2nd Edition : Dec.15,2008-00

1.1 Overview on Software Installation

n Hardware Operation Environment

l With Windows Vista Operating System

l With Windows XP or Windows Server 2003 Operating System

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

n Software Operation Environment

l Correspondence between Windows OS Versions and Service Packs

SP1 SP2 SP3 SP1 SP2 R2 R2 SP2 SP1 SP2 SP2

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

l About Coexistence with Other Software

l Coexistence with PRM

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

n About Coexistence with CENTUM System

Table Correspondence between ProSafe-RS and CENTUM Release Numbers

IM 32S01C50-21E 3rd Edition : Dec.22,2009-00

n Types of ProSafe-RS Software Installations