0% found this document useful (0 votes)
424 views145 pages

PACiS V4.6 ReadMe - G

The document is a readme file for PACiS V4.6.6 software. It contains information on the software components included in the release, such as C264, EQ_SIM, and OI software. It also details some configuration instructions for features like Modbus protocol, PSL automation, network printing, and OI hot redundancy. The record of revision section documents changes between software issues and releases.

Uploaded by

lancenglot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
424 views145 pages

PACiS V4.6 ReadMe - G

The document is a readme file for PACiS V4.6.6 software. It contains information on the software components included in the release, such as C264, EQ_SIM, and OI software. It also details some configuration instructions for features like Modbus protocol, PSL automation, network printing, and OI hot redundancy. The record of revision section documents changes between software issues and releases.

Uploaded by

lancenglot
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 145

CONFIDENTIAL. All rights reserved. AREVA.

Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

DISTRIBUTION

G
AREVA

README
PACiS V4.6

PACiS V4.6.6

BP75
34975 Lattes Cedex - France
AREVA T&D Protection & Contrôle, Avenue de Figuières –
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
Intended blank page

#
$

$ ' (!
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"
NAME

A. COULON

M. VERNEY

B. CLAUSSE

'(('(
POSITION

MANAGER

ENGINEER
PACiS QUALITY
PACiS PROJECT

SES GROUP MANAGER


APPROVAL SIGNATURES

DATE

#
$
SIGNATURE

$) ' (!
RECORD OF REVISION

ISSUE DATE AUTHOR COMMENTS


A 01/10/08 G. JUVANON Delivery of C264 B5.14E, EQ_SIM V1.7.0,
GTW V6.1.2, GTW_PCCN V1.4, OI I.01.07 with
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

SCADA 2000 M4RC74F, P_WATCH V2.7,


SBUS Agency V5.6D, SCE V4.56.6 and SMT
K.01.02
Add information on configuration for SEPAM
Modbus legacy protocol on C264
Add information and configuration for PSL (FBD
automation)
Add Network Printer configuration
Add information on Bay Local OI and virtual
keyboard
Add information and configuration of OI Hot
Redundancy
B 29/01/09 G. JUVANON Delivery of C264 B5.14H, GTW V6.1.4, OI
I.01.10 with SCADA 2000 M4RC74I,
authorization.

P_WATCH V2.8, SBUS Agency V5.8B, SCE


V4.56.9.1 and SMT K.03.02
Add Precision on configuration of Ethernet
Printer
Add information on configuration of memory of
SQL server 2005 and on Clean Historian Log
file
Add information on Consolidation archive files
C 12/08/09 G. JUVANON Delivery of C264 B5.14O, GTW V6.2.7, OI
I.01.16 with SCADA 2000 M4-I.01.16, SBUS
Agency V5.9A, SCE V4.56.9.5 and SMT
K.03.03
Add information on configuration of Ethernet
Board of the PC-GTW
Remove information on configuration of DCOM
for GTW-OC protocol OPC
D 18/11/09 G. JUVANON Delivery of C264 B5.14R1, GTW V6.2.9, OI
I.01.20, SBUS Agency V5.9D, SCE V4.56.9.8
and SMT K.03.03
Add on for C264 software installation (format
flash)
Add procedure to replace a new tztab file into
the SCE

!" # $

% & % '(('( $! ' (!


D1 04/12/09 G. JUVANON Delivery of SCE V4.56.9.8.A and SMT K.03.04
Add information on SMT installation

E 20/01/10 G. JUVANON Delivery of C264 B5.14W, GTW V6.2.12, OI


I.01.22A, SBUS Agency V5.9F, SCE
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

V4.56.9.9.B
Delivery of CR1392: Network names extension
to 15 characters
Add precision on frequency of CPU270 (CPU3)
Add modification on User Documentation (§ 17)
E1 01/03/10 G. JUVANON Add Equipment Simulator (§ 9)
Add Time Stamp on OI documentation
Add modification on Ethernet Switches User
Documentation
F 24/03/10 G. JUVANON Delivery of OI I.01.23, SBUS Agency V5.9L,
SCE V4.56.9.9.C, SMT K.03.05
Delivery of CR1421: GOOSES OUTPUT:
Manual sorting in SCE (§ 12.1)
authorization.

Add information on use of Group SPS status in


IsaGraf (§ 14.3)
Add information on network name on CMT (§
6.1)
Add information on IEC61850/IEC61850
Gateway configuration (§ 18.5)
F1 24/04/10 G. JUVANON Delivery of C264 B5.14X, OI I.01.25
Add information on loading the settings file into
a redundant C264 (§ 6.7)
F2 09/08/10 G. JUVANON Delivery of C264 B5.14Z, OI I.01.26
F3 16/08/10 G. JUVANON Delivery of GTW V6.2.14A, OI I.01.27,
P_WATCH V2.9, SBUS Agency V5.9N, SCE
V4.56.9.9.E, SMT K.03.06
Add information on use of 2 or more SMT
kernel on the same network
Add information on specific WORDS into
ISAGRAF (§ 14.4)
F4 06/10/10 G. JUVANON Delivery of C264 B5.14AA, GTW V6.2.14.3, OI
I.01.28, SBUS Agency V5.9P, SCE V4.56.9.9.F
Add information on Media Sense feature (§
2.2.1)
Add information on PACiSClientWatch (§2.5)

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
G

& %
!"

'(('(
05/11/10
G. JUVANON

#
$
Agency V5.9T, SMT K.03.07
Add note on "stuxnet virus" §1

$ ' (!
Delivery of C264 B5.14AC, OI I.01.29, SBUS
TABLE OF CONTENTS
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

1. GENERAL .....................................................................................................................................................9

2. OPERATOR INTERFACE..........................................................................................................................9
2.1 OI INSTALLATION ........................................................................................................................................9
2.1.1 Standard installation ..............................................................................................................................9
2.1.2 Stand-alone OI client installation...........................................................................................................9
2.2 NETWORK SETTING .....................................................................................................................................9
2.2.1 Media Sense feature................................................................................................................................9
2.3 TIME SYNCHRONISATION SETTINGS ............................................................................................................9
2.4 SQL SERVER 2005.......................................................................................................................................9
2.4.1 SQL Server Agent Service.......................................................................................................................9
2.4.2 Russian Report Templates ......................................................................................................................9
2.4.3 Greek Report Templates .........................................................................................................................9
2.4.4 SQL Server memory................................................................................................................................9
2.4.5 Clean Historian Log file .........................................................................................................................9
2.5 PACIS CLIENT WATCH................................................................................................................................9
2.5.1 Generalities ............................................................................................................................................9
authorization.

2.5.2 User Guide .............................................................................................................................................9


2.6 SOCKET LIMITATION EXTENSION SOFTWARE...............................................................................................9
2.7 CONFIGURATION OF PACIS OI SERVER AS WINDOWS SERVICE...................................................................9
2.7.1 Setup of tools ..........................................................................................................................................9
2.7.2 Configuration of OI Server as Windows Service ....................................................................................9
2.8 OI UNINSTALLATION ...................................................................................................................................9
3. PACIS WATCH ............................................................................................................................................9

4. SYSTEM MANAGEMENT TOOL .............................................................................................................9

5. SYSTEM CONFIGURATION EDITOR ....................................................................................................9

6. COMPUTER C264........................................................................................................................................9
6.1 COMPUTER INSTALLATION...........................................................................................................................9
6.2 SPECIFIC TO THE VERSION ............................................................................................................................9
6.2.1 Introduction ............................................................................................................................................9
6.2.2 Flash re-formatting and new software installation ................................................................................9
6.3 ETHERNET PORT MANAGEMENT ON CPU3 ...................................................................................................9
6.4 RUSSIAN / CHINESE LANGUAGE CONFIGURATION ........................................................................................9
6.5 C264 BOOT PARAMETERS RESTORATION ......................................................................................................9
6.6 TELNET FROM CMT.....................................................................................................................................9
6.7 LOADING MICOM S1 SETTINGS FILE FOR A REDUNDANT C264 ....................................................................9
7. GATEWAY....................................................................................................................................................9
7.1 INSTALLATION .............................................................................................................................................9
7.2 USER DOCUMENTATION ...............................................................................................................................9
8. STATION BUS AGENCY ............................................................................................................................9
8.1 INSTALLATION .............................................................................................................................................9
8.2 USE SBUS AGENCY ....................................................................................................................................9
!" # $

% & % '(('( $* ' (!


9. EQUIPMEMT SIMULATOR......................................................................................................................9
9.1 INSTALLATION .............................................................................................................................................9
9.2 USER DOCUMENTATION ...............................................................................................................................9
10. PC CONFIGURATION ON WINDOWS XP.........................................................................................9
10.1 DEACTIVATION OF SECURITY CENTER .........................................................................................................9
10.2 DEACTIVATION OF FIREWALL ......................................................................................................................9
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

10.3 DEACTIVATION OF "ERROR REPORTING" .....................................................................................................9


10.4 SETTINGS FOR DCOM .................................................................................................................................9
10.5 FOLDERS OPTIONS........................................................................................................................................9
10.6 PACIS OI: SHARED FOLDERS ......................................................................................................................9
10.7 PACIS OI/SMT: NETWORK CONFIGURATION ..............................................................................................9
10.8 PACIS OI: SETTING FOR DCOM ................................................................................................................9
11. TUNNELLING MODE ............................................................................................................................9
11.1 TUNNELLING MODE THROUGH SERIAL PORT ................................................................................................9
11.2 TUNNELLING MODE THROUGH ETHERNET NETWORK ...................................................................................9
11.2.1 Installation of tunnelling components ................................................................................................9
11.2.2 Launch the tunnelling.........................................................................................................................9
12. CONFIGURATION INFORMATION ...................................................................................................9
12.1 SCE CONFIGURATION..................................................................................................................................9
12.1 OI PRINTER CONFIGURATION ......................................................................................................................9
12.1.1 OI Printer: Marked characters ..........................................................................................................9
authorization.

12.1.2 Parallel Printer: Printing spooler configuration ...............................................................................9


12.1.3 Network Printer Configuration ..........................................................................................................9
12.2 COMPUTER PRINTER CONFIGURATION.........................................................................................................9
12.3 TIME CONFIGURATION .................................................................................................................................9
12.4 INTEGRATION OF A NEW RELEASE OF TZTAB FILE ........................................................................................9
13. FBD AUTOMATION ...............................................................................................................................9
13.1 FBD SETTING ..............................................................................................................................................9
13.2 FBD BEHAVIOUR.........................................................................................................................................9
13.2.1 TON/TOFF timer values ....................................................................................................................9
13.2.2 TON behaviour...................................................................................................................................9
13.2.3 TOFF behaviour.................................................................................................................................9
13.2.4 SR Latch .............................................................................................................................................9
13.3 FBD: SEVERAL OUTPUTS .............................................................................................................................9
14. ISAGRAF AUTOMATION .....................................................................................................................9
14.1 SCE: MULTI DO IN THE SAME STEP .............................................................................................................9
14.2 USE OF MPS DATAPOINTS ...........................................................................................................................9
14.3 USE OF GROUP SPS DATAPOINTS.................................................................................................................9
14.4 SCE CONFIGURATION ..................................................................................................................................9
15. OI PRINTER STATES.............................................................................................................................9
15.1 PARALLEL PRINTER .....................................................................................................................................9
15.2 NETWORK PRINTER .....................................................................................................................................9
16. BAY LOCAL OI .......................................................................................................................................9
16.1 PRESENTATION ............................................................................................................................................9
16.2 VIRTUAL KEYBOARD ...................................................................................................................................9
17. OI HOT REDUNDANCY FUNCTION ..................................................................................................9
17.1 SPECIFICATION ............................................................................................................................................9
!" # $

% & % '(('( $+ ' (!


17.1.1 OI Server Fault Tolerance State Automation .....................................................................................9
17.1.2 OI Server functions vs OI Server State...............................................................................................9
17.1.3 OI System datapoints..........................................................................................................................9
17.1.4 Unknown state management...............................................................................................................9
17.1.5 Redundancy performances .................................................................................................................9
17.2 CONFIGURATION AND SETTINGS ..................................................................................................................9
17.2.1 SCE Configuration .............................................................................................................................9
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

17.2.2 OI Setting ...........................................................................................................................................9


17.2.3 SQL Server 2005 configuration..........................................................................................................9
17.2.4 Script Installation...............................................................................................................................9
17.2.5 Connection and remote access configuration on SQL Server 2005 ...................................................9
17.3 CONSOLIDATION ARCHIVE FILES ..................................................................................................................9
17.4 STOP OI HOT REDUNDANCY ........................................................................................................................9
18. ADDENDUM TO USER DOCUMENTATION.....................................................................................9
18.1 C264 USER DOCUMENTATION ADDENDUM – FR13523:...............................................................................9
18.2 OI USER DOCUMENTATION ADDENDUM .......................................................................................................9
18.3 TIME STAMP ON OI......................................................................................................................................9
18.3.1 Time stamp .........................................................................................................................................9
18.3.2 Functional description .......................................................................................................................9
18.4 ETHERNET SWITCH USER DOCUMENTATION ADDENDUM.............................................................................9
18.5 DEFINING IEC61850/IEC61850 PACIS GATEWAY CONFIGURATION ..........................................................9
authorization.

!" # $

% & % '(('( $ ' (!


1. GENERAL
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This document gives simplified indications to install and to configure PACiS V4.6
components. In any case, please refer to the User Manuals to have complete information.

To install PACiS SCE, PACiS OI and PACiS Gateway, you must be the Administrator of the
PC.

Mandatory: the 'Administrator' user must be with password. It must be the same on all
PC of the application.

Operating System:

• Windows XP SP3, Windows XP Embedded (Micom A) for GTW and SMT


• Windows XP SP3 for OI

Don't install the SCE on the same PC as SMT.


authorization.

The PC which supports PACiS OI must not have "HMI" as Network name.

Only One OI Client can be opened in each PC. OI Client must not be minimized and
also must not be stopped by task bar.

Only One SCE can be opened in each PC.

The network name of all equipments on Station Bus can have until 15 characters. It must be
unique among all the devices per Station Bus (except for OI server and OI client). The first
character must be a letter.

With the CMT, the network name must be also less than 15 characters.

Remark:
The Equipment Simulator must be installed on a dedicated PC (i.e. it cannot be installed with
another PACiS application like SMT).

Note on Microsoft Security for Windows XP SP3:

Microsoft has published Technical Security Bulletin MS10-073 for Vulnerabilities in


Windows Kernel-Mode Drivers Could Allow Elevation of Privilege (981957), it concerns
the "stuxnet" virus. More information can be found on Microsoft web site:
http://www.microsoft.com/technet/security/bulletin/MS10-073.mspx.

Microsoft provides an update (KB981957). It's delivered into TOOLS\KB981957 folder.


It's mandatory to install it on PACiS plateforms.

!" # $

% & % '(('( $( ' (!


2. OPERATOR INTERFACE
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In "OI I.01.29" folder you will find:


• the GETTING_STARTED folder which contains the Getting Started Manual
(draft) and the Advanced Topics Manual (draft)
• the LICENCE_CONTRACT folder which contains the software licensing text
• the PROGRAMS folder with :
• the PACiS OI folder which contains the OI application
• the XML Parser folder which contains the OI Parser application (to
install with the SCE)
• the S2K M4 folder which contains the SCADA 2000 application
• the TOOLS folder which contains:
SocketLimitationExtension folder which contains "EvID42226Patch.exe"
authorization.

software to set-up the number of concurrent TCP connection attempts


(see § 2.4)
CleanHistorianLog folder which contains files to install job to flush
periodically the Historian_job file (see § 2.3.5)
Framework .net 2.0 folder which contains file to install Framework .net
2.0 (for use Hard copy)
PACiSOI_Service folder which contains all files necessary to configure
PACiS OI Server as Windows Service (see § 2.5)

2.1 OI installation
For OI Hot Redundancy, see after standard installation (§ 2.1.1) and SQL server
2005 (§ 2.3) § 16.

2.1.1 Standard installation

For PACiS OI Server, it is mandatory to setup a complete installation of PACiS OI


(server & client) and SCADA 2000.

1. Check if SQL Server 2005 is installed (see information § 2.3) – If no, install it

2. If a previous version of OI application is installed, uninstall it, see § 2.8

3. If a previous version of SCADA 2000 application is installed, uninstall it, see §


2.8
!" # $

% & % '(('( $(( ' (!


4. If OI and/or SCADA 2000 applications have been uninstalled, reboot the PC

5. If it's the first setup of PACiS V4.6, delete the Historian Database and Recreate it
by using "Microsoft SQL Server Management Studio"),

6. Launch PROGRAMS\S2K M4\M4-I.01.29_setup.exe to install SCADA 2000


application (custom installation, don't change the default path of the installation
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

(C:\Program Files\USDATA)
authorization.

7. Reboot the PC

8. Launch PROGRAMS\PACiS OI\setup.exe to install the OI application

9. Reboot the PC

Notes:

• The path for the SharedWorkspace and Temp during Installation can't be
modified, even if the custom installation has been selected.

• check the msxml<xy>.dll library file dates in C:/WINNT/system32 or in


C:/WINDOWS/system32 folder : if they are different from those provided in
Tools\msxml\msxml_dlls.zip file (on PACiS CDROM), replace them and do not
install any third-party applications after.

If you can't replace them, it's because the Windows File protection comes into
action and as soon as one writes into the system32 folder the XML files, it
retrieves the old version. To replace them:
use a software which temporarily disables the Windows file protection,
allowing to copy and paste the msxml<xy> dll files.
!" # $

% & % '(('( $( ' (!


Rename the current files (from msxml<xy>.dll to msxml<xy>.dll__), then
copy the new dll files from zip file.

• To be able to visualise the Help file of OI (by clicking on the Help button of the
Command Banner the OI Client), it's mandatory to have the Acrobat Reader
software installed on the PC.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

!" # $

% & % '(('( $() ' (!


2.1.2 Stand-alone OI client installation

For PACiS OI Client stand-alone, it is mandatory to setup an installation of


PACiS OI Client and SCADA 2000 (Client Builder & S2Kserver).

1. During setup of PACiS OI, select custom installation to be able to select Client
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

components only:
authorization.

2. Use the “autologon” (Install Checkup view, Logon button) box to define on which
OI server the client will be connected

3. Be sure to define the same Windows user with the rights on each PC, and log-on
the PC with this user

!" # $

% & % '(('( $(! ' (!


4. Modify the registry on the PC which support the stand-alone OI Client: set
HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\PACIS\Configuration\SharedWor
kspace to the path of the SharedWorkspace folder on the server OI PC. If this key
doesn't exist, you have to create it:

• Add new String Value,


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

• Give "SharedWorspace" as name


authorization.

!" # $

% & % '(('( $( ' (!


2.2 Network Setting
Some networks setting must be set to avoid risk of network anomaly.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

2.2.1 Media Sense feature

Media Sense is a feature of Windows XP/2000 that automatically detects whether


the media are in a link state (on TCP/IP network).

Media Sense indicates if a network cable is disconnected or unplugged from the


Network Interface Card (NIC), a cable modem or router by displaying a message
similar to "Network cable is unplugged" on the TaskBar, or "Media State...: Cable
Disconnected" while using the 'ipconfig' command.

Once Windows operating system detects that the network cable has been
disconnected, the entire network protocol stack is disabled. The Media Sense was
designed to enable the network protocol stack once the network cable is plugged
back into the NIC or cable modem/router, but practically, it is noted that sometimes
this does not work and the network protocol stack remains disabled owing to which
the computer cannot establish a connection to the Internet because Windows Media
authorization.

Sense has failed.

To set Media sense, you need to follow these steps:

1) Start Registry Editor (run regedit)


2) Locate the following registry sub key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
3) Add the following registry entry to the Parameters sub key:
Name: DisableDHCPMediaSense
Data type: REG_DWORD (Boolean)
Value: 1

If key already exists set it at 1.

!" # $

% & % '(('( $( ' (!


2.3 Time Synchronisation Settings
Step 1: Open Adjust Time/Date… of windows time and select the correct Timezone in
accordance to your configuration.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Step 2: In Adjust Time/Date… of windows time, use the Internet Time and enter the
SNTP server IP address

Step 3: In Registry (type Regedit in Execute… of Windows Start menu), go in


HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/W32Time/Paramete
rs and change the period DWORD key to 1E0 (PC will request synchronisation 480
times per day).

Step 4: For OI Server, W32Time will be started by Agency. But for OI Client, there is no
Agency, so put W32Time in Start up of Windows Start menu.
authorization.

!" # $

% & % '(('( $(* ' (!


2.4 SQL Server 2005

2.4.1 SQL Server Agent Service


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Microsoft SQL server Agent service must be running on PACIS OI. So if not running,
you have to start it.

• Open SQL Server Configuration Manager from startup menu

• Select SQL Server 2005 Services


authorization.

Check the state and the Start Mode of SQL Server Agent, if the state is Running and
the Start mode is Automatic, you don't have to do anything, if not do the following
actions:

• Open the properties of SQL Server Agent by clicking right on SQL Server Agent:

!" # $

% & % '(('( $(+ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%

& %
!"

'(('(
Click on Start button:

Click on Apply and on OK


Select the Service Tag and put the Start mode to Automatic:

#
$

$( ' (!
• Check the state and the Start Mode of SQL Server Agent:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

2.4.2 Russian Report Templates

In addition of the Windows language (set as Russian), it is necessary to choose the


"Cyrillic_General" SQL collation during the Windows SQL Server 2005 installation.
authorization.

Uncheck "Case – sensitive", and check "Accent – sensitive"

!" # $

% & % '(('( $ ' (!


2.4.3 Greek Report Templates

In addition of the Windows language (in Greek), it is necessary to choose the


"Greek" SQL collation during the Windows SQL Server 2005 installation.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

Uncheck "Case – sensitive", and check "Accent – sensitive".

!" # $

% & % '(('( $ ( ' (!


2.4.4 SQL Server memory

To limit the use of memory by SQL server, change the maximum server memory. Do
the following actions:

1. Open "SQL Server Management Studio" program and connect to the server
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

name

2. In the left panel, click on "Server name" and select Properties:


authorization.

3. Select memory page, and change "Maximum server memory (in MB)" value to
half of PC memory with a minimum of 1024:

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

4. Then click on OK

2.4.5 Clean Historian Log file

In the “TOOLS/CleanHistorianLog” folder of delivery of PACiS OI, launch the bat


named installCleanLog.bat, it will install the job cleanLogHistorian on MS SQL
Server.

This will be install a new job on SQL Server, this job will be periodically flush the
Historian_log file.

There is not usefull uninstallation procedure. If need, you have to suppress it from
Tool SQL Manager.

!" # $

% & % '(('( $ ) ' (!


2.5 PACiS Client Watch

2.5.1 Generalities
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The PACiSClientWatch application is intended to Watch normal running and freeze


detection of Client Builder application. On startup the application starts same as
WatchOiClient application. Once Client Builder is up, it sends alive message to
PACiSClientWatch application periodically (every 3 seconds). If this message is not
received for configured time, it will mark as frozen and kill Client Builder. If restart is
configured it shall restart Client Builder.

2.5.2 User Guide

2.5.2.1 Configuration

Pacis Client Watch is using ini configuration file to detect settings.

The details are listed below:


authorization.

Configuration File Name: PacisClientWatch.ini


File Location: C:\Program Files\AREVA\PACiS\PacisOI\Client\PacisClientWatch

Configuration options:

Parameter Description
InactiveTimeLimit (ms) Allowable inactive time limit between two consecutive
alive messages. Default is 300. This value can be
changed to change the time of termination of “Client
Builder” application after freeze detection
StopOnFreeze Action to perform after freeze detection. If value is true,
terminate the client on Freeze detection. Default is true
RebootOnStop Action to perform after termination of “Client Builder”. If
value is true, restart the client after Termination. Default
is true

Sample PacisClientWatch.ini file:

[WatchConfig]
InactiveTimeLimit=300
StopOnFreeze=True
RebootOnStop=True

!" # $

% & % '(('( $ ! ' (!


2.5.2.2 User Interface

Startup:

Pacis Client watch can be invoked from desktop shortcut.


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

On startup application goes into hidden mode and show in system tray.
authorization.

Show Log:

Shows the log window:

!" # $

% & % '(('( $ ' (!


Clear Log:

Clear the log window:


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

Exit:

Shut down PacisClientWatch application.

2.5.2.3 Logging

This application logs important events to log file. These trace logs can be used to
detect the sequence of events happened during each run.

Contents of log:

At startup of Client watch application logs the Machine name


Each log has timestamp of the event.
On “Client Builder” start up, it logs the details if it is invoked from Client watch (This
will be same for restart of client).
The details of first alive message from “Client builder”
Details of stop message from “Client builder”
Details of Freeze detection
Termination of Client Builder on freeze detection

!" # $

% & % '(('( $ ' (!


Log Config:

Log File Name: PacisClientWatch.log


Log File Creation: Startup of PacisClientWatch.
Location: Executable Location

Backup:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This application keeps 10 backup form PacisClientWatch#1.log to


PacisClientWatch#10.log

Sample Log:

2010\03\05 18:54:38 PaCISClientWatch Starting on Host : [AFIOS1]


2010\03\05 18:54:38 PaCISClientWatch InactiveTimeLimit = [300] , StopOnFreeze = [True] ,
RebootOnStop = [True]
2010\03\05 18:54:38 PaCISClientWatch Starts with CmdParam
[E:\Areva\Pacis\source\vnest_view_G0307N\PACIS_OI\TOM\Product\Source\FrontVueBinDbg
U\Client BuilderD.exe C:\LocalWorkspace\AFIOS1.fvp /T10]
2010\03\05 18:54:38 Going to start Client
2010\03\05 18:54:38 Client Started PID = [0xac0]
2010\03\05 18:54:38 Alive Event received First time from Client PID = [0xac0]
authorization.

!" # $

% & % '(('( $ * ' (!


2.6 Socket Limitation Extension software
In Microsoft Windows XP SP2 and upper, there is a limitation of 10 concurrent TCP
connection attempts.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This limitation is prejudicial to PACIS OI connection performances.

To extend this limit use the 'EvID4226Patch.exe' software included in the


“Tools/SocketLimitationExtension” folder of delivery of PACiS OI.

We recommend changing the limit to 200.

Follow the steps below for doing this:

1. Execute the 'EvID4226Patch.exe’ software. A command prompt window will


be shown.
2. You will then be asked some questions.
“Do you really want to change the limit to 10?” Type ‘C’ (C=Change limit).
authorization.

3. “Please enter the number of concurrent half-open connections” Type ‘200’

4. “Do you really want to change the limit to 200?” Type ‘Y’ (Y=Yes)

!" # $

% & % '(('( $ + ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

5. “May these files be renamed until end of patching?” Type ‘Y’ (Y=Yes)

6. A countdown (15 seconds) will be started for rechecking the files. During this
authorization.

countdown a Windows File Protection popup might appear. You will be


requested to insert the Service Pack CD. Don’t insert the CD. Just click on
‘Cancel’.

7. Another popup will appear asking you if you are sure to keep unrecognized
file versions. Click on ‘Yes’.

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Note: The countdown and the program execution in the command prompt
window don’t wait for the Windows File Protection pop-ups closing.

8. The program execution in the command prompt window will finish and you will
be asked to press any key to exit. Press a key and reboot the PC to finish the
authorization.

installation.

!" # $

% & % '(('( $) ' (!


2.7 Configuration of PACiS OI server as Windows Service
This chapter describes the configuration of PACiS OI Server as Windows Service for
PACiS OI Server on Windows 2000 Server.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The folder "TOOLS\PacisOI_Service" folder of delivery of PACiS OI contains all


documents and tools to configure OI server as Windows Service.

2.7.1 Setup of tools

1. Unzip "srvany.zip" file into the folder "%SYSTEMROOT%\system32"

2. Copy the file "InstallPacisSrv.bat" into the install folder of SCADA2000 :


"C:_Program files\USDATA\S2K\Bin"

3. Copy the file " PacisSrvkeys.reg" into the install folder of SCADA2000 :
"C:_Program files\USDATA\S2K\Bin"

2.7.2 Configuration of OI Server as Windows Service


authorization.

1. Launch "InstallPacisSrv.bat" file

2. Open the Computer management console (My Computer\Manage)

3. Select PacisSrv and click right to display menu option

!" # $

% & % '(('( $)( ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
4. Select Properties

5. In "General" tab, select "Manual" for the "Startup Type"

#
$

$) ' (!
6. In "Log On" tab, Select "Local System account" and "Allow service to interact
with desktop"
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

7. In "Recovery" tab, configure as follows


authorization.

8. Click on Apply, then go back to the "General" tab, and start the service

9. Once the service started, click on OK

10. Each time, S2Kserver is stopped; the user has to restarted the PacisSrv
service.

!" # $

% & % '(('( $)) ' (!


2.8 OI Uninstallation
The uninstallation procedure is done via the Windows Control panel: “Add/Remove
Programs” item.

Select each installed PACIS components from the list and do the uninstallation.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

After completing the uninstallation of all installed PACIS Components, restart the
machine and make sure that all the folders created during installation and the
registry entries are removed.

Folders to Check:

• $:\Program Files\USDATA
• $:\Program Files\AREVA\PACiS\PACiSOI
• $:\S2K_HMI
• $:\SharedWorkspace
• $:\LocalWorkspace
• $:\Temp\Trace

Registry Keys to Check:


authorization.

PACiS OI:

• HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\PACIS\Configuration
• HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\PACIS\IECCoupling
• HKEY_LOCAL_MACHINE\SOFTWARE\USDATA

XmlParser:

• HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\OdcConfigurationTool
• HKEY_LOCAL_MACHINE\SOFTWARE\USDATA

If any of the folders or registry keys exists, users have to manually remove all those
folders and the keys. Otherwise a further reinstallation could result in a faulty
behaviour of the PACIS System.

!" # $

% & % '(('( $)! ' (!


3. PACIS WATCH
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In "P_WATCH V2.9" folder you will find:


• the LICENCE_CONTRACT folder which contains the software licensing text
• the PRODUCT_INFORMATION folder which contains the User Manual
(draft)
• the PROGRAMS folder with the application (Setup.exe)

The installation of PACiS Watch is mandatory on both PC in case of OI HOT


redundancy use.

Launch Setup.exe to install the PACiS Watch application.


authorization.

In standard installation it is installed automatically in the directory "C:\Program


Files\AREVA\Pacis\PacisWatch".

If it is an initial installation, a "paciswatch.ini" file is delivered in the PacisWatch


directory. As this file is supposed to be adapted by the user (see the User Manual
for more information), the further installations do not replace it, but only adjust the
path of PACiS OI, SMT or Station Bus agency if necessary (see below in case of OI
redundancy).

The installation software asked for the type of the configuration of PACiS Watch
(Executable only or Executable and Service):

Click on No to install PACiS Watch only as executable mode.

At the end of installation the following information message box is displayed:

!" # $

% & % '(('( $) ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In case of "Yes" response, PacisWatch is launched using the initialisation file


present in the installation directory.

If a new release of Pacis Watch have to be installed, it is recommended to install it


directly, without uninstalling the previous one, otherwise, the eventual modifications
authorization.

done in the .ini file will be lost.

Uninstallation:
The uninstallation should be used only if you wish to remove definitely PACiS Watch
from the PC. It can only be performed from the Settings/Control panel/Add/remove
programs panel. Be sure that PacisWatch is stopped before un-installation.
“Uninstall PacisWatch” only performs the removal of files created upon installation.
The files created later by using PacisWatch (like paciswatch.txt) are not deleted.

Nota:

For information in the registry in


HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\PACIS there is a PacisWatch folder
which contains the current_version field and location fields. These fields are filled at
installation and must not be modified.

!" # $

% & % '(('( $) ' (!


4. SYSTEM MANAGEMENT TOOL
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In "SMT K.03.07" folder you will find the SMT application.

Don't install SMT on the same PC as SCE.

1. If a previous version of SMT application is installed, uninstall it


2. If a version of SBUS Agency is installed, uninstall it
3. Install SBUS Agency, see § 8
4. Launch SMT-R3_K.03.07.exe to install SMT application
5. If Framework.net 2.0 is not installed, install it from TOOLS\Framework .net 2.0
(it's necessary to upload disturbance files)
6. Reboot the PC
authorization.

If the SMT is installed on a different PC that an OI Server, the user has to install the
patch ''EvID4226Patch.exe' which is delivered in TOOLS\SocketLimitationExtension
folder of delivery of PACiS SMT, see installation in § 2.4.

Notes:

- The Help menu is no more available: it will be replaced by a direct access to the
User Guide in a further release

- The COMTRADE converters (2001 or 1997) are now directly installed with the
SMT

- A new parameter has been added to the kernel.ini file. This parameter is used
to define an additional storage path for the disturbance files. The disturbance
files will be store in the default directory AND in this additional directory. This
additional directory name may point to a remote PC identified by its IP address
or a network name.
Example:

DisturbanceAlternateStoragePath = \\PCLD533NT5\Disturbance

Where PCLD533NT5 is a remote PC network name and DisturbanceDir a


directory on this remote PC. The remote directory must be shared to allow the
file transfer from the SMT PC to the remote PC.

- A new parameter has been added during the installation process. This version
support both COMTRADE 2001 and COMTRADE 1997 format for the
!" # $

% & % '(('( $)* ' (!


disturbance files. A new dialog box allows the user to select which format will be
used by the SMT. The default format is COMTRADE 2001. This option can be
changed by editing the Kernel.ini file located in the Program
files\Areva\SMT\exe directory.

Change the line DisturbanceConvertersPath=C:\Program


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Files\AREVA\Pacis\Smt\disturbance_converters\COMTRADE2001” to
DisturbanceConvertersPath=C:\Program
Files\AREVA\Pacis\Smt\disturbance_converters\COMTRADE1997 to switch
from 2001 to 1997 revision year of the COMTRADE standard.

- Use of 2 or more SMT Kernel on the same networks (or on networks being
connected)

If you install 2 or more SMT kernel on the same network (or on networks being
connected), you must define specific broadcast addresses for each SMT kernel.
This can be chosen during installation process.
authorization.

Or by editing the kernel.ini file and hmi.ini file in the SMT installation directory
(default folder

C:\Program Files\AREVA\PACiS\Smt\exe). You need to change both ini files !

You need to change to following values:

SysDBmcastAddress=230.0.0.250
EquipmentMcastAddress=230.0.0.251
LogMcastAddress=230.0.0.252

Those addresses are used by the kernel to send information’s to the HMIs

!" # $

% & % '(('( $)+ ' (!


5. SYSTEM CONFIGURATION EDITOR
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In "SCE V4.56.9.9.F" folder you will find:


• the SCE_4.56.9.9.F.installer.exe file which allows the SCE application
installation

Don't install SCE on the same PC as SMT.

1. If a previous version of SCE application is installed, uninstall it

2. Launch SCE_4.56.9.9.F.installer.exe

3. Launch "C:\Program files\AREVA\PACiS\sce\4.56.9.9.F\data\cal\setting\vcredist_x86\


vcredist_x86.exe" to install correctly this library - If it is not correctly installed, the
setbuilder program to produce the setting files of C264 may not work.
authorization.

4. If a previous version of OI parser application is installed, uninstall it

5. Launch PROGRAMS\XML Parser\setup.exe (in OI I.01.29 folder)

If the SCE is not installed on the same PC as PACiS OI, do the followings:

6. If a previous version of SCADA 2000 is installed, uninstall it

7. Launch PROGRAMS\S2K M4\ M4-I.01.29_setup.exe (in OI I.01.29 folder) to


install only Client Builder application

8. Reboot the PC

During installation, the "lax.nl.java.option.java.heap.size.max" attribute is set


automatically to 2/3 PC RAM size, max 1.3 GB.

!" # $

% & % '(('( $) ' (!


Notes :

• Check the msxml.dll file dates in C:/WINNT/system32 or C:/WINDOWS/system32


folder : if they are different from those provided in Tools/msxml_dlls.zip file (on
PACiS CDROM), replace them and do not install any third-party applications after.

If you can't replace them, it's because the Windows File protection comes into
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

action and as soon as one writes into the system32 folder the XML files, it
retrieves the old version. To replace them:
Use software which temporarily disables the Windows file protection,
allowing to copy and paste the msxml<xy> dll files.
Rename the current files (from msxml<xy>.dll to msxml<xy>.dll__), then
copy the new dll files from zip file.

• Install ISaGRAF workbench 4.12

• Using USB dongle, install the dongle management software: Sentinel Protection.
This software is available at : Driver dongle

• To compile ISaGraf project for PACiS SCE and if Microsoft Access 97 is not
installed, you need to install the ODBC driver (dataacc.exe) provided in the MS
Office 97 Value Pack, available either from :
authorization.

• http://www.microsoft.com/ (google key words : Office 97 ValuPack)


• or at the direct address (but which could change) :
http://www.microsoft.com/downloads/details.aspx?FamilyID=F9DFA82C-
9A3B-40DF-B6E4-DC15E6112BBC&displaylang=en

• The ISaGraf workbench cannot be launched from the redundant computer in the
SCE. The following procedure must be applied:
• Launch the ISaGraf workbench from the PLC of the main computer in the
SCE,
• Open the "hardware architecture" window (look at the window menu),
• Click on the graphical link between the ETCP network and the "config1"
equipment to select it,
• Right-click on this link and choose the "property" menu,
• Modify the IP address (i.e. replace the IP address of the main C264 with
the IP address of the redundant one).

• To disable merge of Isagraf functions when a PLC contain only one function, add
in SCE.lax : -Dsce.NoPLCMergeForOneFunction="true"

!" # $

% & % '(('( $! ' (!


6. COMPUTER C264
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

In "C264 B5.14AC” folder you will find:


• the Computer_B5.14AC.exe file which allows the computer application
installation

To install a computer, you need:

• a PC on the Ethernet network

• a C264 computer with at least the BIU241 board and the CPU260 board
flashed with the "bootrom" program

For CPU270 (CPU3):

CPU270 has the following key features:


authorization.

• ) , - , . / + * 0 1 23
/4 5 0"64 5 43 / 4 - 10
• ( + 7
• ! 8 4
• 9
• :

!" # $

% & % '(('( $!( ' (!


6.1 Computer installation
Launch Computer_B5.14AC.exe.

See next paragraph to change the "bootrom" file of the CPU.


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Warning:

The FTP server software is configured with the default installation path (C:\Program
Files\Areva\PACIS\Computer). If this path has been modified, you must modify the
FTP server parameters.

The computer has a default factory IP address and alias, this need to be changed to the
application specific values.
The settings to enter are:

• 4 $ . . ;
• $ 4 4 . <
4 4 ( 4 "
authorization.

• ! $ 4 4 .

Other parameters should not be modified.

!" # $

% & % '(('( $! ' (!


6.2 Specific to the version

6.2.1 Introduction
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

From release C264 B5.14R1 and above, it's mandatory to format the C264
Flash memory using the below procedure.

6.2.2 Flash re-formatting and new software installation

6.2.2.1 Configure the computer for a Network boot

Select the computer in "computer's list" menu

Click on "parameters" menu button.

Select "Network boot"

Fill with the right values: IP on Ethernet and IP 2 on Ethernet


authorization.

Fill with the right value: host IP (the address of your PC)

Validate clicking on "Set boot parameter".

!" # $

% & % '(('( $!) ' (!


The FTPD server must run on the host machine.

Click menu button "Reboot computer"


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

6.2.2.2 Stop C264 application

After reboot complete, select the computer.

Project boards:

Set the computer mode to “Stopped”:

Select the computer in "computer's list" menu

Click on "Stop computer” menu button.

The computer mode can be red using “Computer version” menu button.
authorization.

6.2.2.3 Erase and Format FLASH

After reboot complete, select the computer.

As there is no security message indicating the computer state.

Verify first the computer state it must be STOPPED or BOOT MODE.

In "File explorer" menu click on button "Flash format"

!" # $

% & % '(('( $!! ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
Messages:
Click "YES"
Confirmation pop-up:

00x% done

Wait few minutes before format flash ending.


Flash formatting progress:

#
$

$! ' (!
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Click "OK"

Reboot computer (Click menu button "Reboot computer")

6.2.2.4 BootInstall

Select computer and in "BootInstall" go to the installation directory of the calculator.

For a default installation the directory may be


authorization.

"C:\Program Files\Areva\PACIS\Computer\C264_cpu3"

!" # $

% & % '(('( $! ' (!


Click on "Start: bootInstall"

Project boards:

This message appears:


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Bypass the security if necessary: Click "NO"

All boards:
authorization.

Click "YES"

Messages:

/flash/bin/filename: Resent frames x/yyy

Total installation progress


Wait message "BootInstall finished!”

!" # $

% & % '(('( $!* ' (!


6.2.2.5 Set back computer parameters to Flash Boot

Click on "Parameters" menu button.


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

Select "Flash Boot" and click on "Set boot parameter".

In case of error, fill out the field IP 2 on Ethernet with a correct value.

Production boards:

This value IP2 address is lost after the computer restart.

!" # $

% & % '(('( $!+ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
6.2.2.6 Restart computer

Reboot the computer (Click menu button "Reboot computer")

#
$

$! ' (!
6.3 Ethernet port management on CPU3
The configuration of the both Ethernet ports is made by CMT:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

The IP address of both Ethernet ports must be on two different sub-networks by


configuration (CMT) and also by physical connection.

The 2 CPU3 Ethernet ports can be configured as follows:

N° Port 1 Port 2 Comments


1 IEC61850 SBUS + SCADA IP 2 2 independent SCADA
SCADA IP 1 protocols with different
database
2 SCADA IP 1 SCADA IP 2 2 independent SCADA
protocols with different
database
3 IEC61850 SBUS SCADA IP

Nota: The existing SCADA protocols are DNP3 and T104. You can't have DNP3 on
both ports.

IEC 61850 Station Bus, if configured, is always on port 1.

One or 2 IP SCADA protocols can be configured on port 1 and/or 2 by CMT

!" # $

% & % '(('( $ ' (!


6.4 Russian / Chinese language configuration
If the installed Windows XP is not Russian or Chinese, it's proposing you to choose
the language used by the PC.

For non-occidental languages: Russian (cyrillic) or Chinese, the PC have to be


configured to support Cyrillic or simplified Chinese fonts.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This modification is mandatory to use CMT for such languages.

From the program "Start\Parameters\Configuration Panel\Regional Options"


authorization.

Click on Advanced Tab, select the Russian for Russian or Chinese (Popular
Chinese Republic) for simplified Chinese.

Reboot the PC to apply these changes.

!" # $

% & % '(('( $ ( ' (!


6.5 C264 boot parameters restoration
The aim of this chapter is to describe how to restore C264 boot parameters. It could
be useful after a wrong maintenance action if boot parameters have been
suppressed.

Needed Tools
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

A Personal Computer is needed. Any Windows operating system can be used. The PC
hardware requirement is:

• = . ) / 0
•( . 4 1
The PC software's needed is:

• = /6 6 <2 . 6 >0 ?
The Serial COM terminal is configured for serial communication with:

• 66@
•( ? '
authorization.

•+ .
It should be care of selecting into PC application the PORT 1 or 2 that is physically wired to
the computer.

Communication wiring

The serial link between PC PORT and MiCOM C264 Maintenance port is made via RS232C
straight line.

!" # $

% & % '(('( $ ' (!


DB 9 DB 9

5
1 1
5

6 9 1 1
9
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

2 2 6
3 3
4 4
5 5
Computer 6 6 PC serial PORT
MiCOM C264C 7 7
8 8
9 9

OR
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
C0076ENa
authorization.

Figure 1: Serial Link

Connect the RS cable between the MiCOM C264 and the PC, and run the hyper-terminal
program. If the parameters and wiring are correct, the connection is established.
Restart the C264 with a power reset and stop the first count down with any key. The
following prompt is displayed:
[VxWorks Boot]:

Checking default settings: p command

CR is the Carriage Return done with “Enter” key of the PC keyboard.


At the prompt type the following:
[VxWorks Boot]:p CR
The following information should be displayed:

A : $ B <
A. $
A4 $C 4 D
A $' 4' ':EF 1
A 4 $C ! EEE"EEE"EEE"EEED
A 1. $
A4 $C 4 EEE"EEE"EEE"EEED
A - $ """
A $C D
!" # $

% & % '(('( $ ) ' (!


A .. - $C . - D
A $ E
A $C D
A . . $
A 4 $
[VxWorks Boot]:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Settings to enter

The settings to enter are: -

• 4 $ . . - 1
• 4 $ . . ;
• $ 4 4 .

• ! $ 4 4 .

• .. - $86 < 4 86 : ,
authorization.

. 1 . 4 !G .
!G . ) H . - 4 4 . - :EF 1
Other parameters should not be modified.

Input new settings: c command

It is now time to configure with the “c” command the communication settings of the MiCOM
C264 Computer.
Enter the Configuration Command:
[VxWorks Boot]: c CR
Each parameter is displayed one by one with each CR. If a mistake is press CR several
times, then restart the operation again.
The stored value is displayed. If nothing is entered, pressing CR will keep the stored
parameter.
The “.” key allows the replacement of the stored value by nothing.
[VxWorks Boot]:
[VxWorks Boot]: p CR
The following information should be displayed:

A : $ B <
A. $
A4 $C 4 D
A $' 4' ':EF 1

!" # $

% & % '(('( $ ! ' (!


A 4 $C ! $EEE"EEE"EEE"EEED
A 1. $
A4 $C 4 $EEE"EEE"EEE"EEED
A - $ """
A $C D
A .. - $C . - D
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

A $ E
A $C D
A . . $
A 4 $
[VxWorks Boot]:
Now restart the computer with the new parameters, either with a power reset, or by typing:
[VxWorks Boot]: @ CR
After the reboot the computer C264 is ready for receiving the application software. See C264
Installation manual to go a head.

6.6 Telnet from CMT


authorization.

The "Telnet" button from the CMT tool launches the default Windows Telnet client
on the operator PC. Telnet is connected to the selected computer.

This tool asks for a login "c264" and a password "areva264".

This login and this password are the same for each Computer.

!" # $

% & % '(('( $ ' (!


6.7 Loading Micom S1 Settings file for a redundant C264
For a Redundant C264, do the following actions to load settings file:

1. Load the Micom S1 settings file into the Active C264


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

2. Make a switch of both C264 to change the former Standby C264 to Active
C264

3. Load the Micom S1 settings file into the new Active C264
authorization.

!" # $

% & % '(('( $ ' (!


7. GATEWAY
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

7.1 Installation

In "GTW V6.2.14.3" folder you will find:


• the GTW_6.2.14.3.exe file which allows the gateway Legacy application
installation
• the GI74 folder which contains installation documentation (draft)
• the OPC-client folder which contains clientopc_1.1.exe &
serversurclientopc.exe files
authorization.

1. If a previous version of gateway application is installed, uninstall it

2. If a previous version of SBUS Agency is installed, uninstall it

3. Install SBUS Agency, see § 8

4. Launch GTW_6.2.14.3.exe to install gateway application

5. Reboot the PC

Note:

Gateway with OPC Protocol:

In "clientopc_1.1.exe" file, you can find:

- The installation of an client OPC for test “ClientTst.exe,

- The procedure for register OPC foundation DLLs.

The "setup serveursurclientopc" can be used to register the server on the client.

!" # $

% & % '(('( $ * ' (!


7.2 User documentation
1 - PACiS GTW-PC: Protocol T101 registry key:
[HKEY_CURRENT_USER\Software\alstom\Te\T101\Protx_COMy\Configuration\
- " nb_counter_sample " : to specify the behaviour of the transmission of
counter datapoints:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

- 0 : the value of counter is sent to the SCADA each sample,


- #0 : the value of the counter is cumulated each sample and this calculated
value is also sent to SCADA each sample. This calculated value is set to
0 each "nb_counter_sample".

When this mode is used, don't send a ‘counter interrogation’ from SCADA
because this operation sends a ‘reset+freeze’ request. So, the value is
erased and will be indicated as ‘invalid’.

2 - A registry key has been added to avid creating traces on disk:

Key = HKEY_LOCAL_MACHINE\SOFTWARE\AREVA\PACIS\TG\MAIN\flag_log
(0 no write else 1 or 2 write)

If Windows XP embedded the key is always created with value = 0.


authorization.

If Windows XP the key is always created with value = 1.


This key is periodically read (period (heartbeat or maintenance_dcnx_ethernet)). The
key can be set at any time.
If the key value = 2 then when the Gateway restarts the key will be written with the
value 1 to allow the write while the start.
If the key value = 0 or 1 then when the Gateway restarts the key will be written with
the value 0 if Windows XP embedded or 1 if Windows XP (default values).

3 - Ethernet Board of PC-GTW:

In case of only one Ethernet board on the gateway and several IP address, Station
BUS IP address must be the first while typing "ipconfig" request on a DOS session.

To do so, if user needs to add an IP address in connection parameter he/she must


first remove SBUS IP address, then add the required IP address(the Station BUS IP
address). User must check that Station BUS address is the first by typing "ipconfig"
request. In such case, a good practice is to have one Ethernet board for SCADA
Bus, the other one Ethernet board for Station Bus

!" # $

% & % '(('( $ + ' (!


8. STATION BUS AGENCY
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

8.1 Installation

In "SBUS V5.9T" folder you will find:


• the Agency_V5.9T.exe file which allows the Station Bus application
installation

1. Uninstall the previous agency

2. Launch Agency_V5.9T.exe to install the Station Bus application as described


authorization.

below

In the “License agreement” window, click on “I accept the agreement”, then on “next”

!" # $

% & % '(('( $ ' (!


Then in the "Select Destination Location", define the installation folder and click on
"next" (the default installation folder is C:\Program Files\Areva\PACIS)
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

In the "Select Components" window, select the chosen components to install


(XP/2000 Install or XP embedded)

In the "Select Start Menu Folder" window, select where the shortcut to launch the
Agency will be available (in PACiS folder by default)

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
4. Reboot the PC
Then click on "Next" then on “Install” to install the components.

#
3. Install WinPcap software, during the same setup of SBUS Agency

$ ( ' (!
Note1:
The agency must be installed on each PC which supports the OI server, the SMT,
and the Gateway.

Note2:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

During installation, Dr Watson is enabled and configured with specific parameters; if


other applications are installed after SBUS Agency and alter the Dr Watson
parameters, the exception handling may have an un-expected behaviour. So it is
advised to check before running SBUS Agency that the following registry
parameters are these ones.
authorization.

VisualNotification = 0

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Auto = 1
Debugger = drwtsn32 –p %Id –e %Id -g
authorization.

8.2 Use SBUS Agency


Each sub-system runs each own SBUS Agency.

SMT launches SBUS Agency at the first connection of a device, so the colour of the
SMT icon in the system tray at the start up of SMT is yellow.

An attribute has been added in the SCE to configure TCP/IP address for SMT. This
address must be different than OI address.

!" # $

% & % '(('( $ ) ' (!


For using SMT and OI on the same PC, you must add the SMT TCP/IP Address in
second address for Local Area connection properties, advanced TCP/IP settings.
First Address is OI Address
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

On Windows XP, in this case of two Internet Protocol (IP) address on the same
network board, after a disconnection of the Ethernet network, the primary address is
reset to 0.0.0.0; the primary IP address is not restored after the network cable is
reconnected.

Microsoft provides a hotfix, see http://support.microsoft.com/kb/896062/en-us


authorization.

!" # $

% & % '(('( $ ! ' (!


The agency.log file is in the following directory:

- For SMT :

C:\Program files\AREVA\PACiS\Smt\SBUS

- For OI:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

C:\Program files\AREVA\PACiS\PACiS OI\Server\Configuration\DBID1\


S2KHMIConfig\S2K-HMI-SRV\UCA2

C:\Program files\AREVA\PACiS\PACiS OI\Server\Configuration\DBID2\


S2KHMIConfig\S2K-HMI-SRV\UCA2

You can acces to Edit Flag (MVLLOG and OdLogLevel) with regedit:
Key : HKEY_LOCAL_MACHINE\AREVA\PACIS\UCA2Agency
authorization.

!" # $

% & % '(('( $ ' (!


9. EQUIPMEMT SIMULATOR
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

9.1 Installation

In "ES V1.7.0" folder you will find:


• the EqsV1.7.0.exe file which allows the Equipment Simulator application
installation

1. If a previous version of Equipment Simulator application is installed, uninstall it

2. If a previous version of SBUS Agency is installed, uninstall it

3. Install SBUS Agency, see § 8


authorization.

4. Launch EqsV1.7.0.exe to install Equipment Simulator application

5. Reboot the PC

9.2 User documentation


The limit of lines in a scenario file (extension .ess) is 500.

!" # $

% & % '(('( $ ' (!


10. PC CONFIGURATION ON WINDOWS XP
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This chapter describes the process to use PACiS components on Windows XP


Operating System (for OI/SMT and Gateway).

The Windows XP OS must be set-up as "Administrator".

After power-on the PC, go to the session of Administrator


authorization.

If there is no "Administrator" username displayed, click twice on "Ctrl+Alt+Suppr",


then enter the username "Administrator" and the corrected Password.

!" # $

% & % '(('( $ * ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
Start>Settings>Control Panel

Click on "Administrators Tools"


10.1 Deactivation of Security Center

Click on "Performance and Maintenance"

#
$

$ + ' (!
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"
menu:

'(('(
Click on "Component Services"

#
$

$
' (!
Select "Security Center" from "Services (Local)" item. Click right on Properties
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Select "Disabled" for the "Startup Type", then click on OK.


authorization.

10.2 Deactivation of Firewall


From "Components Services", select "Windows Firewall/Internet Connection:

Click right on "Properties" menu:


!" # $

% & % '(('( $* ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Select "Disabled" for the "Startup Type", then click on OK.


authorization.

10.3 Deactivation of "Error reporting"


In order not to make inoperable function like OIClientWatch, it is necessary to
deactivate the “error reporting” Microsoft functionality for Windows XP.

To proceed deactivation, go to "Control panel" and choose "System". Open the


"Advanced" tab and choose "Error reporting

!" # $

% & % '(('( $*( ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
Set the option "Disable error reporting".

#
$

$* ' (!
10.4 Settings for DCOM
This chapter describes the configuration of Windows for DCOM access. In this
configuration, the user name "EveryOne" is mandatory. If it dosen't exist, create it
(Add menu)
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

1. Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to


configure permissions:
authorization.

2. Click on "Components Services"

3. Click on "Computers"

4. Click on "My Computer" on control panel and select "Properties"

5. Go to "Default Properties" tab, set "Default Authentification Level" to


"Connect" and "Default Impersonation Level" to "Identify"
!" # $

% & % '(('( $*) ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
6. Go to "COM Security" tab

7. Click on "Edit Limits in "Access Permissions" item

#
$

$*! ' (!
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

8. For all Groups and user names, allow "Local Access" and "Remote Access",
authorization.

then click on OK

9. Do the same on "Edit Default"

10. Click on "Edit Limits in "Launch and Activation Permissions" item

!" # $

% & % '(('( $* ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

11. For all Groups and users names, allow "Local Launch", "Remote Launch",
"Local Activation" and "Remote Activation", then click on OK

12. Do the same on "Edit Default"


authorization.

!" # $

% & % '(('( $* ' (!


10.5 Folders options
Launch "Explorer" software, Tools item, Folders options, View Tab, deselect the last
line "Use simple file sharing (Recommended), then click on OK:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

10.6 PACiS OI: Shared Folders


For each shared folders:

- C:\SharedWorspace

- C:\Temp\trace

- C:\Program files\AREVA\Pacis\PacisOI\Server\MemoFolder

The sharing has to be configured as follows:


!" # $

% & % '(('( $** ' (!


1. C:\SharedWorspace:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Select "Permissions" and for "Everyone", Allow "Full control", "Change" and "Read".
authorization.

2. C:\Temp\trace:

Select "Permissions" and for "Everyone", Allow "Full control", "Change" and "Read".

!" # $

% & % '(('( $*+ ' (!


3. C:\Program files\AREVA\PACiS\PACiSOI\Server\MemoFolder:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

10.7 PACiS OI/SMT: Network configuration


For using SMT and OI on the same PC and with only one network board, you must
add the SMT TCP/IP Address in second address for Local Area connection
properties, advanced TCP/IP settings. First Address is OI Address.

On Windows XP, in this case of two Internet Protocol (IP) address on the same
network board, after a disconnection of the Ethernet network, the primary address is
reset to 0.0.0.0; the primary IP address is not restored after the network cable is
reconnected.

Microsoft provides a hotfix, see http:\support.microsoft.com/kb/.896062/en-us

!" # $

% & % '(('( $* ' (!


10.8 PACiS OI: Setting for DCOM
1. Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

configure permissions on "S2K.OpcServer" component.

2. Select "S2K.OpcServer", click right and select Properties


authorization.

3. Select Security Tab, set "Use Default" for "Launch and Activation
Permissions" and for "Access Permissions", set "Customize" for
"Configuration Permissions"

!" # $

% & % '(('( $+ ' (!


4. Click on "Edit…" for "Configuration Permissions"
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

5. For all Group and user names, allow "Full Control" and "Read", then click on
OK

6. Do the same configuration of Security for "SCADA 2000 C2KAlarmServer"

7. Do the same configuration of Security for "SCADA 2000 Server.exe"

!" # $

% & % '(('( $+( ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
#
8. Go to "Location" Tab, select "Run application on this computer"

$+ ' (!
9. Do the same configuration of Security and Location for "NewClusterMgt"
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

10. Do the same configuration of Security and Location for "USDATA Trend
Datasource Server"
authorization.

11. Go to "Identity" Tab, select "The interactive user"

!" # $

% & % '(('( $+) ' (!


11. TUNNELLING MODE
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The tunnelling mode allows to connect the MiCOM S1 setting software to a legacy
MiCOM IED using:
• a serial port of the computer
• or the Ethernet network

11.1 Tunnelling mode through serial port

Computer
front port
• Hyper-terminal
authorization.

• MiCOM S1
C264

tunnel
Legacy port
(Modbus or
T103)
IED

1. Check that MiCOM S1 is correctly installed

2. Launch the hyper-terminal on the PC (the baud rate is 19200 bauds, no parity)

3. Verify you have the prompt (“>”) on the hyper-terminal

4. The following commands allow to have information on tunnelling mode :

• TunnelingRSState allows to know if the tunnelling function is used

• TunRSLines gives on which legacy ports a tunnel can be opened

!" # $

% & % '(('( $+! ' (!


• TunRSIed <line number> gives the list of connected IED on the
<line number> line and their address

• TunRSStart <line number>,<IED address> allows to open a


tunnel between the PC and the IED

• TunRSStop allows to close the tunnel


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

5. Open a tunnel with the TunRSStart command and stop the hyper-terminal

6. Launch the MiCOM S1 in rear port mode and use it as usual (be careful to
the baud rate and the parity which must be 19200 bauds and no parity)

Note: if there is no exchange between the IED and the setting software during
two minutes, the tunnel is automatically closed.

11.2 Tunnelling mode through Ethernet network


authorization.

• PatuSpy software
• UCA2 agency
• MiCOM S1

Ethernet network
(UCA2)
C264

tunnel
Legacy port
(Modbus or
T103)
IED

!" # $

% & % '(('( $+ ' (!


11.2.1 Installation of tunnelling components

1. Install the MiCOM S1 software

2. Install the Station Bus agency (see § 8). Verify you have requested the
installation of “IED PACiS tunnelling” component (all files for tunnelling are in
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

<installation folder>\Tunneling folder)

3. Launch PATDbWin and set your parameters (Edit menu). Then close
PATDbWin.
authorization.

4. Launch the Install_oncrpc.bat file (warning: this file should be modified if the
installation folder of tunnelling components is not the default one)

5. Launch the Portmap service:


• Open the Windows Configuration Panel
• Open the Services manager
• Select the PortMap service
• Click on the “Starting …” button, choose “automatic start-up” and click on
OK
• Click on the “Start” button
• Close the Services manager

!" # $

% & % '(('( $+ ' (!


6. Install the tunnelling dlls in the MiCOM S1 folder:
• For Modbus: copy the dll S1V2ModdbusPatu.dll into the folder "..\Micom
S1\S&R-Modbus" and rename it SRModBus.dll

• For T103: copy the dll S1V2T103Patu.dll into the folder "..\Micom S1\S&R-
103" and rename it W32KommDll.dll
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

7. Modify the C:\WINDOWS\system32\drivers\etc\hosts file to include the list of the


computers you want to connect to. Insert the string “# Begin_PATU_configuration -
do not remove this comment” before the list of computer addresses. Insert the
string # End_of_PATU_configuration - do not remove this comment” after the list of
computer addresses. Example:

# Begin_PATU_configuration - do not remove this comment


192.2.120.1 mypc
192.2.120.3 yourpc
# End_of_PATU_configuration - do not remove this comment
authorization.

!" # $

% & % '(('( $+* ' (!


11.2.2 Launch the tunnelling

1. Launch the LaunchS1V2Patu.exe file


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

2. Verify the location folder of the MiCOM S1

3. Select the protocol (Modbus or T103)

4. Enter the IP address of the computer on which is connected the IED

5. Enter the line number on which is connected the IED

6. Enter the IED address

7. Click on “Launch MiCOM S1 V2”

!" # $

% & % '(('( $++ ' (!


12. CONFIGURATION INFORMATION
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

12.1 SCE Configuration

1) SCE: Tap Changer: Management of Higher/Lower Position & Goto min/max


datapoints
authorization.

! " #
- $ ! #
%

%
& '
" (
- $ ! #
#
- )

)
- )

) '
* # +,-!- &-,+" '

!" # $

% & % '(('( $+ ' (!


2) C264: Local Alarm Acknowledgement

In addition to the Global Alarm Acknowledgement SPS, a Local Alarm


Acknowledgment SPS can be defined on a per C264 basis (i.e. one per C264).

This SPS can be wired, managed by an automation or associated to a control.


When this SPS is configured in a C264, the "Global Alarm Acknowledgement"
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

SPS is no more taken into account by this C264.

When this SPS is SET, all C264 alarms are immediately acknowledged.

This SPS cannot be transmitted on the Station Bus network (i.e. it remains local
to the C264).
authorization.

!" # $

% & % '(('( $ ' (!


3) C264: Autorecloser Type 2 (PCCN)

A new built-in function has been added: Autorecloser Type 2.


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

4) C264: Synchrocheck Type 2 (Terna)

A new synchrocheck Internal manual has been added: Type 2


authorization.

5) GTW: T101 protocol: Balanced mode management

On GTW Slave protocol T101, 3 new attributes have been added under a new
category "Balanced mode":
• Balanced mode (Y/N), default N
• Balanced mode retry number (from 1 to 10), default 3
This attribute defines, in balanced mode, maximum of repetition on non
acknowledged frame
• Balanced mode link timeout (from 2000 to 10000), default 2000
This attribute defines, in balanced mode, a timeout between a gateway
information frame and SCADA acknowledgement

Note: These 3 attributes are no more in registry. The user has to define them by
configuration

!" # $

% & % '(('( $ ( ' (!


6) SCE: Goose ranking

A new attribute 'Goose rank' has been added under all type of dataObject.
This attribute contains the rank of dataObject inside the goose messages (in
SCL or .dm files). It is set to 0 by default. This value indicates that rank is
undefined. It can be modified by the user to indicate the real goose rank of the
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

dataObject.

During an auto-addressinf og the C264


authorization.

The defined (<>0) 'goose rank' are not updated if the dataObject is still "transmitted
by goose".
The defined (<>0) 'goose rank' are reset with an undefined value (0) if the
dataObject is not "transmitted by goose".
The undefined (=0) 'goose rank' are set to the last used rank into the whole 61850
mapping.

During an auto-addressing of the C264(s)

The Automatic Addressing dialog box allows selecting a new option of 61850 auto-
addressing: 'reset of goose rank' for each C264 (available for multiple or single auto-
addressing). This option is available through a check box not selected by default.
If the check box ‘reset of goose rank' is selected then all goose ranks of 61850
mapping are reset with an undefined value And all goose ranks are re-computed in
a new order.

!" # $

% & % '(('( $ ' (!


12.1 OI Printer Configuration
SOE and/or Log Book printers can be managed using parallel or Ethernet network
printer.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

It is not allowed to mix parallel and network printers.

The use of parallel printers is not allowed in Hot Redundancy mode.

12.1.1 OI Printer: Marked characters

To be able to print French characters (marked characters), you must select the
code page 1004 on the Lexmark 2591/2591n printer. Refer to the printer manual to
modify this code.

12.1.2 Parallel Printer: Printing spooler configuration

Printing service uses Windows spooling primitives. There are some requirements on
spooler configuration in order to ensure an optimize functionality:
authorization.

1. Remote printers used in PACiS OI have to be declared in local spooler,


2. For printer, printing mode has to be defined Like this:
− In “Ports” tab, Port timeout (Transmission retry) has to be defined to 2 in
order to defining a faster error detection,

− A : I < - . 4 : $
- : <
(<
. . . 4 .
. <
. <
: . "

!" # $

% & % '(('( $ ) ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
#
$

$ ! ' (!
12.1.3 Network Printer Configuration

For configurating a SOE Network Printer (Lexmark 2591n), no specific action is


needed with the SCE (as usual, the printer's name in the configuration should match
the printer's name as defined in Windows).
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The only difference is that the TCP/IP port used by the printer must start with "IP_".
This is not done by default, so after installing the printer, add a new TCP/IP port
from Windows as described below:

1. Open the Configuration Panel and go to "Printer and Faxes"

2. Right-click on the installed SOE network printer and choose "Properties"


authorization.

3. Choose "Add Port"

4. Choose "Standard TCP/IP Port"

5. Choose "New Port"

!" # $

% & % '(('( $ ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
6.

& %
!"

'(('(
Click on "Next" on the following screen

#
$

$
' (!
7. Type the printer's IP address of the printer and click on "Next". Windows
automatically adds the "IP_" prefix to the port number as Port name
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

8. Select "Generic Network Card" and click on "Next"


authorization.

9. Select "Finish" in the last screen

10. Close the previously opened "Printer Ports" window

11. In the Printer properties, choose the port you have created and click on "Apply"

!" # $

% & % '(('( $ * ' (!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

12. The SOE network printer is attached to the port created.

13. In "Advanced" tab, following options have to be selected:


authorization.

- : <
(<
. . . 4 .
. <
. <
: . "

(!" Click on Apply then on OK

!" # $

% & % '(('( $ + ' (!


12.2 Computer Printer Configuration
To be able to print French characters (marked characters), the "characters font"
ISO 8859-15 must be selected on the EPSON LX300 printer. Refer to the printer
manual to modify this font.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

!" # $

% & % '(('( $ ' (!


12.3 Time Configuration
External Clock: UTC

Time Zone: Country locale


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The local time is available on all sub-system except at the SCADA level, where the
events are dated in UTC time.

Loss of External Clock source: the C264 Master Clock continues to synchronise the
other equipments. A TS fault is set to 1.

All PC (PACiS OI, PACiS GTW, and PACiS SMT) must be configured with the same
time zone, normally country timezone.
authorization.

!" # $

% & % '(('( $( '(!


12.4 Integration of a new release of tztab file
In the SCE, the tztab file is in the directory: 'C:\Program
files\AREVA\PACiS\SCE\<version_SCE>\data\cal'.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

1. Check the compatibility

Be sure that the new tztab is compatible with the file included into the release of
SCE:

1.1 - Index of country must be constant


Example: if index:
288:USA Central:UTC-6:-360:DST: -6hours (Local summer -5 hours)
exists in the current file, a line with the same index (288) must exist in the new
file.
If a new index exists in the new file, it will not be take into account.

1.2 - The data associated to the index can be different:


authorization.

Example: the line:


288:USA Central:UTC-6:-360:DST: -6 hours (Local summer
-5 hours)
288S:0:2:8:14:3:0: second March
Sunday at 2:00
288W:0:2:1:7:11:0: first November
Sunday at 2:00
Can be replaced by:
288:USA Central:UTC-6:-360:DST: -6 hours (Local summer
-5 hours)
288S:0:2:1:6:4:0: first Avril
Sunday at 2:00
288W:0:2:25:31:10:0: last October
Sunday at 2:00

2. Replace the current file by the new file

If both files are compatibles with syntax described above, the current file can be
replaced by the new file.

!" # $

% & % '(('( $( ( '(!


13. FBD AUTOMATION
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

13.1 FBD Setting


New parameters have been added for FBD: FBD Timer and FBD Boolean
authorization.

For TON/TOFF timers, the “timer value” input can be associated:


• to a direct value (today’s behaviour)
• to a “timer setting” input (FBD Timer)

input
TON /
TOFF
Timer value output

Associated to this timer setting, the user can define its name (on 16 characters), the
range of values, the step (the unit is milli-seconds), and if the parameter is visible
read-only, visible modifiable or not visible in the Micom S1.

!" # $

% & % '(('( $( '(!


A maximum of 100 “Timer settings” can be defined on a per C264 basis, whatever is
the number of PSL configured in the computer.

In the C264, the timer setting is taken into account at the next evaluation of the
TON/TOFF operator (i.e. when the input changes).
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

For Boolean operators (i.e. AND, OR, XOR, NOT operators only), one (and only
one) input can be defined as a parameter

Input x
Logical
Operator
Input y output

Boolean Parameter

(the Boolean parameter input is managed as all others Logical Operator inputs).
authorization.

The attributes of a Boolean parameter are:


• the short name, with 16 characters
• the default value (0 or 1)
• the labels associated to 0 and 1 values, with 16 characters (for example,
0=”desactivated”, 1=”activated”)

• the editable in Micom S1 : Visible read-only, visible modifiable, not visible

A maximum of 100 “Boolean parameters” can be defined on a per C264 basis,


whatever is the number of FBD configured in the computer.

In the C264, the Boolean setting is taken into account immediately (i.e. managed as
the modification of an operator input).

A maximum of 50 FBD can be defined with Timer settings / Boolean settings.


!" # $

% & % '(('( $( ) '(!


13.2 FBD Behaviour
Reminder: in FBD (and only in FBD), transient SPS are transformed in permanent
SPS. A “reset” state is created 1ms after the “set” state.

13.2.1 TON/TOFF timer values


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

TON/TOFF values are allowed between 50 ms and 1 hour, with a 10 ms step.

Regarding previous timer values, the SCE provides:


• an upgrade which allows to automatically modify TON/TOFF timer values > 50
ms which are not with a 10 ms step to the nearest lower value
• a new check which indicates if it exists TON/TOFF timer < 50 ms and in which
PSL
• an improvement of the FBD editor : when launching the FBD editor, a pop-up
window is displayed if it exists TON/TOFF timer < 50 ms, with the message
"invalid TON/TOFF timer exists, they will be erased. Do you want to continue ?"
:
o if NO : the FBD is closed and previous timer values are not modified
authorization.

o if YES : the FBD is opened and timer values < 50 ms are erased.

13.2.2 TON behaviour

input
TON output
T

The TON operator aims to maintain the output state to “0” during the T timer when
the input becomes different from “0".

The T timer is reinitialised when the input state becomes “0” whatever is the
previous state (i.e. “1” or Invalid)

!" # $

% & % '(('( $( ! '(!


Event Input = 0 Input = 1 Input = INV T expiration
State

Not initialized Output = 0 Output = 0 Output = INV X


Goto state 1 Activate T Goto state 3
0 Goto state 4
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Output = 0 X Activate T Activate T X


Goto state 4 Goto state 5
1

Output = 1 Output = 0 X Output = INV X


Goto state 1 Goto state 3
2

Output = INV Output = 0 Output = 0 X X


Goto state 1 Activate T
3 Goto state 4

Input = 1, Output = 0 Stop T X Goto state 5 Output = 1


and timer activated Goto state 1 Goto state 2
4

Input = INV, Output = 0 Stop T Activate T X Output = INV


and timer activated Goto state 1 Goto state 4 Goto state 3
authorization.

X is a forbidden action: it means the computer will go in Halt mode.

13.2.3 TOFF behaviour

input
TOFF output
T

The TOFF operator aims to maintain the output state to “1” during the T timer when
the input becomes different from “1”.
The T timer is reinitialised when the input state becomes “1” whatever is the
previous state (i.e. “0” or Invalid).

!" # $

% & % '(('( $( '(!


Event Input = 0 Input = 1 Input = INV T expiration
State

Not initialized Output = 0 Output = 1 Output = INV X


Goto state 1 Goto state 2 Goto state 3
0

Output = 0 X Output = 1 Output = INV X


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Goto state 2 Goto state 3


1

Output = 1 Activate T X Activate T X


Goto state 4 Goto state 5
2

Output = INV Output = 0 Output = 1 X X


Goto state 1 Goto state 2
3

Input = 0, Output = 1 X Stop T Goto state 5 Output = 0


and timer activated Goto state 2 Goto state 1
4

Input = INV, Output = 1 Goto state 4 Stop T X Output = INV


and timer activated Goto state 2 Goto state 3
5
authorization.

X is a forbidden action: it means the computer will go in Halt mode.

13.2.4 SR Latch

S
SR latch Q
R

The SR latch aims to maintain the Q state to “1” when the S input is set, and
maintain the Q state to “0” when the R input is set. When both inputs are at “0”, Q
state is unchanged. When both inputs are at “1”, Q is forced to reset.

X is a forbidden action: it means the computer will go in Halt mode.

Q-1 is the output value before the reinitialization (stored in the C264).

At first Boot (after change of data base) Q-1 =0.

N.B.: A change of software without a change of database is not considered as a first


boot Q-1 is the memorised one.

!" # $

% & % '(('( $( '(!


Event S=0 S=1 S = INV R=0 R=1 R = INV End of init
State

Not initialized VAR= Q-1 VAR=1 VAR= Q-1 VAR= Q-1 VAR=0 VAR= Q-1 X
Goto state Goto state Goto state Goto state Goto state Goto state
0 1 1 1 2 2 2

Not initialized, X X X Goto state VAR=0 Goto state X


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

waiting R init 3 Goto state 3


3
1

Not initialized, Goto state If R=1, Goto state X X X X


waiting S init 3 then 3
VAR=0,
else
VAR=1
Goto State
2 3

Not initialized, X X X X X X Q=VAR


waiting end of init If Q=0 goto
state 4
else goto
3 state 5
authorization.

Q=0 No Action If (R=0 or No Action If S=1 No Action No Action X


4 R=INV) Q=1
then Q=1 Goto
Goto state State 5
5, else no
action
Else No
Action

Q=1 No Action If R=1 then No Action No Action Q=0 No Action X


5 Q=0 Goto state
Goto state 4
4, else no
action

I1, I2, 2 inputs of RS latch.

The origin of those inputs can be:

• Directly acquired by C264’s BIU

Acquired trough an IED (IED legacy or IED on SBUS).

I1 or I2 can be temporary “lost” in case of lost of source of information. Example in


case of reboot of C264, disconnection of the IED sever of I1, I2, …

!" # $

% & % '(('( $( * '(!


I1 I2 S R Q

1 0 1 0 1

1 1 - - 1 Lost of source of information and I2 changes

1 1 1 1 0 Retrieval of source of information


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

I1 I2 S R Q

1 0 1 0 1

0 1 - - 1 Lost of source of information and I1 I2 change.

0 1 0 1 0 Retrieval of source of information

I1 I2 S R Q

1 1 1 1 0
authorization.

1 0 - - 0 Lost of source of information and I2 changes

1 0 1 0 1 Retrieval of source of information

!" # $

% & % '(('( $( + '(!


13.3 FBD: Several outputs
In case of several outputs included into a FBD, each output must be connected to a
independent logical block (for example AND) like this figure:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

This following FBD is not correct:


authorization.

!" # $

% & % '(('( $( '(!


14. ISAGRAF AUTOMATION
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

14.1 SCE: Multi DO in the same step


Advices for using ISaGraf in case of multi DO in the same step:

Wait_Ack_Order

It's possible to have several Wait_Ack_Order (maximum 10) in the same


step, under the condition to get back the return's value in an
intermediary variable. Once the returned acknowledge, the reference of
the control is suppressed and doesn't exist any more, so every new call
of this function will send the FALSE return value.

The function Wait_Ack_Order must be into a N step (run every cycle).


authorization.

Send_Binary_Order / Send_Digital_Order

The state of these functions is false if the number of control in progress


is greater than NB_MAX_ISA_CONTROL (currently 1000).

The function Send_Binary_Order must be into a P1 step (run only one


time).

The function Send_Digital_Order must be into a P0/P1 step.

!" # $

% & % '(('( $(( '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"

'(('(
Exemple:

#
$

$((( '(!
14.2 Use of MPS datapoints
The use of MPS Datapoints is particular:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The MPS values inside IsaGraf (via the debugger) are from 1 to 16, whereas in the
C264, the values are from 0 to15.

14.3 Use of Group SPS datapoints


authorization.

In IsaGraf, the group SPS states are seen as OPEN (value 4) and CLOSE (value 5)
and not RESET (value 1) and SET (value 2).

14.4 SCE configuration


Do not use specific words in ISAGRAF workbench: in the ISAGRAF dictionary, some
WORDS concerning XPC orders are defined with “\” or space characters. If we use
those WORDS, we have compilation errors in ISAGRAF.

WORDS concerned (examples):

• ORDER_OFF / ORDER_OPEN
• ORDER_ON / ORDER_CLOSE
• SELECT_OFF / SELECT_OPEN
• SELECT_ON / SELECT_CLOSE

!" # $

% & % '(('( $(( '(!


15. OI PRINTER STATES
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The event printer (LB or SOE printer) state is translated inside the OI to an MPS
value. This MPS is usually known as “Printer Status”. Some new states are treated.

This feature is available only if the printer is connected to the server LPT (parallel) or
TCP/IP port (network) of the PACiS OI Server and was tested with a “LexMark 2400
series” printer. If you plan to use another printer, please ensure that the status
display works properly.

Summary table of the printer status and the corresponding values of the MPS:

15.1 Parallel Printer


authorization.

Printer Status MPS State

Printer Ok STATE0
The printer is in an error state STATE2
The printer is offline STATE4
The printer is out of paper STATE8
Printer is power off or disconnected STATE11
Unexpected value STATE12

15.2 Network Printer

Printer Status MPS State


Printer Ok STATE0
The printer is suspended STATE1
The printer is offline or out of paper STATE4
Require user intervention STATE10
Printer is power off or disconnected STATE11

!" # $

% & % '(('( $(() '(!


16. BAY LOCAL OI
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

16.1 Presentation

The PACiS OI can be used as Bay Local OI with the following constraints:
• Compatible with TouchScreen
• A virtual keyboard can be used
• Controls coming from this OI are accepted by a C264 when the bay local
mode is Local
Audible alarms are not managed in Bay Local OI. An external klaxon cannot be
associated to the audible alarm. All information can be archived, but not printed (i.e.
the bay local OI doesn’t manage printers).
authorization.

From a configuration point of view, the Bay Local OI is seen as a single machine,
composed of one client and one server. No additional OI clients can be added. The
server cannot be redundant.

Each Bay Local OI has its own graphical workspace. It can be client of one or
several IEC61850 servers.

Limits checked by the SCE:


• A maximum of 500 Datapoints can be managed by the Bay Local OI
• Up to 5 mimics, 1 alarm/state/event viewer and 1 trend viewer can be
defined
• FSS viewer cannot be configured

!" # $

% & % '(('( $((! '(!


16.2 Virtual keyboard
A virtual keyboard can be used on Touch Screen.

This virtual keyboard "osk.exe" is located in "C:\Windows\system32" folder. It can be


launched directly or by used the menu "Start\All
Programs\Accessories\Accessibility\On-Screen Keyboard".
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Be careful: Launch this virtual keyboard before launching PACiS OI Client, to be


able to log-on.

This virtual keyboard can also be launched by the OI application, by configuring with
the SCE a "run application" button.
authorization.

!" # $

% & % '(('( $(( '(!


17. OI HOT REDUNDANCY FUNCTION
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

17.1 Specification
The OI Server Redundancy is managed through a set of 2 OI servers named
Cluster.

The OI Clients can be connected on one of the 2 servers. Their configurations are
such as :
o at least one client must have its preferred server declared as Server 1
o at least one client must have its preferred server declared as Server 2
(reminder: each client has in its configuration the list of servers on which it has to be
connected. The first server in this list is the “preferred” server and the client will try to
connect on it first).
authorization.

After the configured inactivity period (used for the automatic logout if configured), an
OI client which is not connected to its preferred server has to try to re-connect to its
preferred server. A pop-up is displayed on the OI client to indicate this re-
configuration.

Client A Client B Client C

Server 1 Server 2

SQL database SQL database

IEC 61850 Station Bus

!" # $

% & % '(('( $(( '(!


Both servers perform datapoints acquisition from IEC61850 servers simultaneously,
and the redundancy mechanism allows consolidating each datapoint change on
each server, to insure that real-time data and historical data are the same on both
servers.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

17.1.1 OI Server Fault Tolerance State Automation

OI Servers are managed via a state algorithm. The 2 servers are marked in
configuration (Server 1 and Server 2).

START UP

STANDALONE WAIT
authorization.

GOING TO
STANDALONE

MASTER SLAVE

SHUTDOWN

• START-UP : starting of the OI server application


o START-UP -> WAIT: The Starting OI Server is Server 2 and the
Server 1 is in the Start-Up state
o START-UP -> SLAVE: The Starting OI Server found the other OI
Server in standalone mode
o START-UP ->STANDALONE: several possibilities:
The starting server is not configured for redundancy ,
the other server is not running,
the starting server is Server 1 and the server 2 is starting.

!" # $

% & % '(('( $((* '(!


• WAIT: only the Server 2 can be in this state. It is waiting for the server 1 to
move to the STANDALONE state
o WAIT -> SLAVE: the server 1 moves to the STANDALONE state with
the same configuration
o WAIT -> STANDALONE: the server 1 is lost.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

• STANDALONE: the server is running alone. If it is configured for


redundancy, it is able to accept connection from the other server and able to
detect the twin master failure.
o STANDALONE -> MASTER: the other server is successfully
connected and the internal state transfer is done.
o STANDALONE -> SHUTDOWN : the server receives a synchronized
shutdown notification
• MASTER: the server is allowed to generate controls. It checks periodically
the health of the other server.
o MASTER -> GOING TO STANDALONE : the other server is lost or is
shutting down, and it remains consolidating message to proceed
o MASTER -> SHUTDOWN : the server is shutting down
• SLAVE: the server is not allowed to generate controls. It checks periodically
authorization.

the health of the other server.


o SLAVE -> GOING TO STANDALONE : the other server is lost or is
shutting down, and it remains consolidating message to proceed
o SLAVE -> SHUTDOWN : the server is shutting down
• GOING TO STANDALONE :
o GOING TO STANDALONE -> STANDALONE : The last consolidating
message received before the lost of the other servers has been
processed
• SHUTDOWN : the server is shutting down

!" # $

% & % '(('( $((+ '(!


Start-up - the 2 OI servers are connected on Ethernet network and visibles:

Server 1 Server 2

START-UP START-UP
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

STANDALONE WAIT

MASTER SLAVE

OI Server Master shutdown + restart:

Server 1 Server 2
authorization.

MASTER SLAVE

PC halted

GOING TO
STANDALONE

STANDALONE

PC start-up

START-UP

SLAVE MASTER

!" # $

% & % '(('( $(( '(!


Start-up – at least 1 OI server is not connected on Ethernet network:

Server 1 Server 2

START-UP START-UP
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

STANDALONE STANDALONE

Ethernet connexion

Case 1 : no OI client connected on OI server 1

SHUTDOWN

START-UP
authorization.

SLAVE MASTER

!" # $

% & % '(('( $( '(!


Start-up – at least 1 OI server is not connected on Ethernet network:

Server 1 Server 2

START-UP START-UP
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

STANDALONE STANDALONE

Ethernet connexion

Case 2 : OI server 2 with less OI clients connected than OI server 1 (means


that the number of OI clients connected is exchanged between OI servers)
SHUTDOWN

START-UP
authorization.

MASTER SLAVE

The management of the OI client number connected to each server to elect the
Master allows avoiding the case where all OI clients are connected to the Server 2
(both servers are Standalone) and this one is shutting-down to allow the Server 1 to
become Master.

17.1.2 OI Server functions vs OI Server State

Master OI Server can:


o Perform acquisition from the IEC 61850 network servers
o Be connected to OI Client(s)
o Performs archives (SQL Historian), alarm management.
o Accept controls from the OI Client directly connected to it, as well as controls
issued from OI Client connected to the OI Server Slave, and manage them
(propagation to the IEC 61850 network)

Slave OI Server can:


o Perform acquisition from the IEC 61850 network servers
o Be connected to OI Client(s)
o Performs archives (SQL Historian), alarm management.

!" # $

% & % '(('( $( ( '(!


o Propagate controls from OI Client connected to it up to the Master OI Server
which will manage the control. The Slave OI Server does not manage
directly controls and does not propagate them to the IEC 61850 network

Standalone OI Server can:


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

o Perform acquisition from the IEC 61850 network servers


o Be connected to OI Client(s)
o Performs archives (SQL Historian), alarm management.
o Accept controls from the OI Client connected to it, and manage them
(propagation to the IEC 61850 network). In this case, there is no control
uniqueness management as both Standalone OI Server can send
commands on the IEC 61850 network (control uniqueness will be performed
at C264 level).

The 2 OI Servers manage their own parallel printer(s). There is no management of


shared printers in case of OI redundancy.
authorization.

17.1.3 OI System datapoints

Each server has to manage its own system datapoints, which have not to be
consolidated between servers (i.e. system datapoints of server 1 are independent of
system datapoints of server 2, but each server has to be aware of the status
changes of the system datapoints of the other server).

The IEC61850 server Status Link datapoint is considered as OI server datapoint.

17.1.4 Unknown state management

An IEC61850 server can be seen as disconnected from an OI server and connected


from the other OI server.

In this case, datapoints from this IEC61850 server will be seen in their current state.

17.1.5 Redundancy performances

The loss of Ethernet connection between 2 OI servers is detected in less than 40


seconds.

The time of re-connection of an OI client to an OI server is less than 120 seconds


(i.e. disconnection from a server + connection to a new server).

!" # $

% & % '(('( $( '(!


17.2 Configuration and settings

17.2.1 SCE Configuration

To define the OI Hot redundancy function:


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

1) Define fully an OI Server

2) Define the OI Client(s) and declare the OI Server as server

3) User the “create backup” function to create the secondary OI Server. Do not
add anything in this secondary server

17.2.2 OI Setting

In HOT redundancy mode, PACiS Watch software must be active.

It is needed for restart automatically the server remote in case of double


STANDALONE and in case of loss of one the servers.
authorization.

17.2.2.1 First Installation

On both PCs, do the following actions:

1) Delete Historian Database

2) Recreate a new Historian Database, see below characteristics of size and log
file

!" # $

% & % '(('( $( ) '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

3) Start OI Server

4) Download the Database into OI Server by SMT


authorization.

5) Switch OI Server

6) Once OI Server is on the current Database, stop it

7) Do the actions described into "SQL Server 2005 configuration" paragraph (§ 16.2.3)

8) Do the actions described into "Script Installation" paragraph (§ 16.2.4)

9) Check the names of all jobs in SQL Server Agent tab, jobs must be
'CleanLogHistorian', 'HistorianConsolidation', and 'PURGE_...' for purge table. If
there are others jobs, you have to delete it (example: 'PARTIAL_...'):

10) Do the actions described into "Connection and remote access configuration of
on SQL Server" paragraph (§ 16.2.5)
!" # $

% & % '(('( $( ! '(!


11) Restart OI Server

17.2.2.2 Change database

Once the database loaded into OI Server, do actions described into "Script
Installation" paragraph.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

17.2.3 SQL Server 2005 configuration

1. Execute the batch file C:\Temp\Trace\HRSQLScripts\install1.bat (where


C:\Temp\Trace\HRSQLScripts = Persistance PACiS shared directory)

2. Wait until the closing of the DOS windows

3. Launch SQL Server Configuration Manager from the windows start menu:
"Programs\Microsoft SQL Server 2005\Configuration Tools
authorization.

SQL Server Agent:

4. Select "SQL Server 2005 Services"

5. On the principal panel, select "SQL Server Agent"

6. Open the property menu (by right click)

!" # $

% & % '(('( $( '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

7. Select "This account" and fill field "Account Name" and "Password" with the data
authorization.

of the Administrator account (Password is mandatory)

8. Click on Apply and on OK (Note the service must be started, if not Click on Start)

Protocols for MSSQLServer:

9. Select "SQL Server 2005 Network Configuration", open this menu

10. Select "Protocols for MSSQLSERVER"

!" # $

% & % '(('( $( '(!


11. On the principal panel, set to enabled the status of :

- Shared memory,
- Named Pipes,
- TCP/IP
To set status enabled, open properties box by a right click on the item
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Remark: VIA is not important


Client Protocols:

12. Select "SQL Native Client Configuration", open the menu

13. Select "Client Protocols"


authorization.

14. On the principal panel, set to enabled the status of:

- Shared memory,
- Named Pipes,
- TCP/IP
To set status enabled, open properties box by a right click on the item
Remark: VIA is not important

!" # $

% & % '(('( $( * '(!


17.2.4 Script Installation

1. Open (by Notepad) the text file


C:\Temp\Trace\HRSQLScripts\Installation\InstallConfiguration.sql

2. In this file, search the text below:


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Find this line to set variable

3. In the next line, you will find two variables to set:


@localServer
@remote Server
4. Set the name of computer's name, which contains OI Servers

Warning:

Be sure you put the correct name, and these names must be crossed on each
server.

Example, at left the text on server OISM, at right the text on server OISR
authorization.

SET @localServer = ‘OISM’ SET @localServer = ‘OISR’


SET @remoteServer = ‘OISR’ SET @remoteServer = ‘OISM’

5. After the variable setting, save and close the file

6. Execute batch file C:\Temp\Trace\ HRSQLScripts\install2.bat

7. Wait until the closing of the DOS windows

8. Reboot the PC

17.2.5 Connection and remote access configuration on SQL Server 2005

Server Properties:

1. Launch "Microsoft SQL Server management Studio" application

2. Select the first menu (<PC_NAME> (SQL Server…)

3. Open the properties box (via the contextual menu/right click)

!" # $

% & % '(('( $( + '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

4. Select Security page

5. Check "Enable server proxy account"


authorization.

6. Fill "Proxy account" and "Password" of the administrator


7. Check "Cross database ownership chaining"

!" # $

% & % '(('( $( '(!


8. Select Connection page
9. Check "Allow remote connection to this server"
10. Check "Require distributed transactions for server-to-server communication"
11. Set Remote timeout to 0 (no timeout)
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

12. Click on OK
Security options:
13. From this tool, expand the tree view until reaching the node "Security\Logins"

!" # $

% & % '(('( $() '(!


14. For each of the following logins:
- NT AUTHORITY\SYSTEM
- BUILIN\ADMINISTRATORS
Open the properties of the login by right-clicking on it from the tree view and
selecting "Properties" from the contextual menu
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

15. In "Server Roles" page, give all rights (check all boxes on server roles panel)
authorization.

16. In "User mapping" page, for each database, check the "Map" box, and check all
boxes on 'Database role membership' panel

!" # $

% & % '(('( $()( '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

17. Click on OK (do the same for others)


18. Reboot the PC

17.3 Consolidation archive files


With the introduction of the Hot Redundancy a new kind of CSV (Archive) files are
generated in the “\SharedWorkspace\ArchivePacis\” directory. They contain the
consolidated data issued from the Hot Redundancy mechanism. Their names have
the suffix “_c” (standing for “consolidated”) to distinguish them from the old kind CSV
that are still generated but that contain only the data from the local server without
any data consolidation between servers.

List of new CSV files generated:

• S2KEventMsg_Table_c
• S2KVTQ6_VTQTimeTable_c
• S2KDaily_VTQTimeTable_c
• S2KMonthly_VTQTimeTable_c
• S2KAnnual_VTQTimeTable_c

!" # $

% & % '(('( $() '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

Since they are generated via SQL scripts and not by the OI Server, these files are
not written at the same time as the old kind of CSV, they ensure first the data
consolidation before performing any writing.

WARNING:

While restoring the CSV files, only the old kind of CSV FILENAMES are taking into
account (without ‘_c’ suffix). Therefore, if any file with ‘_c’ suffix is present into the
“ToRestore”directory during the restoration, an error message will appear in the
ScadaTrace:

“Table name '… _c' is not in accordance with to be archived Historian tables”

Eventhough, the other files will be correctly restored.

For restoring the consolidated CSV files they should be first renamed to match the
old kind of CSV filenames (delete the suffix ‘_c’).

!" # $

% & % '(('( $()) '(!


17.4 Stop OI Hot redundancy
In the Hot Redundancy there is an additional option for stopping the OI Servers
described here below:

When right-clicking on the OI Server icon in the task bar the following contextual
menu is displayed:
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

Here we can choose among:

a. Stop: This will stop both servers (Master and Slave).


b. Stop local server: This will stop only the server from where the stop request
was performed.
authorization.

!" # $

% & % '(('( $()! '(!


18. ADDENDUM TO USER DOCUMENTATION
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

18.1 C264 User documentation addendum – FR13523:


It has been noted a mistake in the user documentation ref: C264/AP and C264P/AP

Here below is the correction:

For User Documentation C264P/EN AP/C41 Page 79/352 Chapter 4.7.2.7


Change
[...]
For Modbus protocol:
SetPoint address on Modbus is only available for WAGO relay, where output
format is fixed
to UINT16.
[...]
authorization.

By:
For Modbus protocol:
SetPoint address on Modbus is only available for WAGO relay, where output
format is fixed
to UINT15.
[...]

For User Documentation C264/EN AP/C40 Page 64/328 Chapter 4.7.2.7


Change
[...]
For Modbus protocol:
SetPoint address on Modbus is only available for WAGO relay, where output
format is fixed
to UINT16.
[...]

By:
For Modbus protocol:
SetPoint address on Modbus is only available for WAGO relay, where output
format is fixed
to UINT15.
[...]

!" # $

% & % '(('( $() '(!


18.2 OI User documentation addendum
OI/EN HI/C40:

2.2.4. State Viewer


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

2.2.4.1 States visualisation and printing

The information which can be displayed about a state is:

• 6 .: $
4 4 4 4 : <
JKJ 4 4 4 4 : 4
. = :
4 4 4 : "
• 7 $ 4 4 " 64 7 L 6
"64 . M ' ' 44$ $ " M"

authorization.

= $ . 4 4 . / E . C
D'C : : D'C D 4 . 4
: 0
• # $ 4 .
• $: 4

. . 4 4 . 4
E /: - 4 4 1 : - 0 A
I"64 . . - 4 4 . 4 -
"

!" # $

% & % '(('( $() '(!


18.3 Time stamp on OI

18.3.1 Time stamp


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The time-stamp is a numeric value representing the date of a datapoint, command


or another type of information on PACIS system.

The time-stamp is a date, storage on an 8 bytes structure, with precision of 10-7


second. It is propagated in the refresh data-flow and in the control data-flow.

18.3.2 Functional description

A quality is defined for time-stamp; it is the time-stamp validity field.

There is two type of time-stamping:

- Time-stamping by the source,


- Time-stamping by the S2K server.
authorization.

18.3.2.1 Time-stamped by the source

In this case time-stamp is set by the source.

In some particular cases, these time-stamp and validity might be overridden by the
S2K server; this is defined in the next paragraph.

18.3.2.2 Time-stamped by the S2K server

Reminder: The datapoint generated by S2K server are time tagged by S2KServer.

There are two cases for the time-stamped by the S2K server.

Case 1: Refresh is older than the last refresh, for the same object (”jump backward
to the past”):

This case is applicable for IED and S2K datapoints.


The S2KServer sets the time-stamp value by adding 1 ms to the previous event, the
time validity is no-synchronised.
This to respect chronology, time-stamps must increase each refreshments destined
to a given object.
Case 2: Local object refresh due to a control operation:

Treatment:

The S2K server sets the time-stamp value. The source is the S2K server.

!" # $

% & % '(('( $()* '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
& %
!"
7. CONNECTION

'(('(
Document : H15x EN GL/B23
18.4 Ethernet Switch User documentation addendum

Figure MICOM H1xx CONNECTION (in Industrial PC)

#
$

$()+ '(!
7.1 - Fault indication contacts

4-RsEp Default 3-RpEs Default


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

1-2 Common
authorization.

Figure Fault Indication CONTACTS

Pin No. Contact meaning


1 Common Vdc
2 Common Vdc
3 RpEs Alarm
4 RsEp Alarm

A closed contact means an alarm or a fault.


The male connector reference is a WR-MPC4 4.20mm Male Dual Row Angled Header 4 way

WIRING RECOMMENDATION: For safety reasons and for compliance with the European
Commission Low Voltage Directive (73/23/EEC), the authorized voltage rating to be applied
on the "Fault Indication relay" is limited to 75 Vdc or 50 Vac and should not exceed 5A.

!" # $

% & % '(('( $() '(!


18.5 Defining IEC61850/IEC61850 PACIS Gateway configuration
Document GTW_EN_C50

6.2. Configuring the GTW in the upper network


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

The actions described below are the first actions the user has to process.
1. Open the upper database (Energy_upper.mpc) and delete all IEC physical devices
from system part (Scs), all FBD equations. Don’t change the name of the substation.
2. In case of multiring arcitecture (i.e. the use of IEC61850/IEC61850 gateway), the OI
which is client of the IEC/IEC gateway will be able to display interlock viewer.
Note: the ILK bypass is not allowed from this OI
3. On the system part, add an" IEC generic IED", set its short name, long name, network
name and its TCP/IP address the same as the IEC61850/IEC61850 GTW on the
lower network, in our example: GTWT101M and TCP/IP address: 192.169.0.55
authorization.

4. From the GTW, launch the "Edit relation" in the contextual menu, click on the tab
"To", click on the item "manages: Bay [0..65535]".

!" # $

% & % '(('( $(! '(!


The list of bays which can be managed by the GTW is displayed. Select those you want to
be managed by the GTW, then click the Apply button. Datapoints you wish to use on the
upper network need to be part of the selected bays.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

!" # $

% & % '(('( $(!( '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

5. On GTW_IEC, change the short name and long name of the Operating mode of the
GTW_IEC. These names must not be the same as name of Operating mode of the
GTW on the lower network

!" # $

% & % '(('( $(! '(!


CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
6.

& %
!"

'(('(
server to be compatible with upper network.

#
$

$(!) '(!
Change the "short name", "long name", "network name" and "TCP/IP address" of OI
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.

%
7.

& %
!"

'(('(
#
$
At this stage, you can import the xml model GTW_IEC_PROT1_13.3.xml file.

$(!! '(!
8. Click on “Import…” to brows the PC in order to find out the xml file
9. In the upper bow , select the xml file, then in the bottom listbox, select the GTW then
Click on “Set” button (a message box is displayed “IED model import in progress
please wait”)
10. Click on “Close” (a message box is displayed “IED model setting in progress, please
wait")
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

At the completion of the import process, check that all "has for IEC address" relations in the
electrical part are filled with the right logical device.
11. Fill the relation between OI server and IEC/IEC GTW (named "has for IEC61850
server").
12. Check in the upper database.
13. If ATCC automatism is present in lower database, do not validate the option "IEC data
model optimisation" (menu Tools/options)
14. Generate the upper database
authorization.

!" # $

% & % '(('( $(! '(!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy