SQL Installation Guide Pacis 4.4
Short Description
Download SQL Installation Guide Pacis 4.4...
Description
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.
AREVA PACiS PACiS V4 README V4.4
DISTRIBUTION Confidentiality Category Restricted
Control Category
Normal
Controlled
Not Controlled
Identification number
Identification letters
Issue
Transmission & Distribution
2059660
RM
C
AREVA T&D Protection & Contrôle, Avenue de Figuières – BP75 34975 Lattes Cedex - France
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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 2 / 173
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.
APPROVAL SIGNATURES
NAME
POSITION
JM. BOISSET
PACiS PROJECT MANAGER
M. VERNEY
R&D VALIDATION & SUPPORT GROUP MANAGER
B. NAL
PACiS QUALITY ENGINEER
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
DATE
SIGNATURE
Identification Number: 2059660 Page: 3 / 173
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.
RECORD OF REVISION
ISSUE
DATE
AUTHOR
COMMENTS
A
08/01/07
G. JUVANON
Delivery of C264 VB4.46, EQ_SIM V1.6.3, GTW V4.19, OI G.02.00B with SCADA 2000 M4RC46B, SCE V4.41.B, SBUS Agency V3.31 and SMT J.03.01 Adding information on PIX Template Adding information on Unused Templates filter and Automatic Documentation for FBD in the SCE Adding information on Toggling Events on T101/T104 and AI scaling (GTW configuration) Adding information for Tap Changer Datapoints management
B
09/03/07
G. JUVANON
Delivery of C264 VB4.48A, GTW V4.21.1, OI G.02.02B with SCADA 2000 M4RC48A, SCE V4.42.B, SBUS Agency V3.32 and SMT J.03.03 Adding information on Automatic Documentation for wiring and SCADA in the SCE Adding information on ISaGraf: multi DO in one step Adding information on C264: DNP3 unsolicited messages configuration (CRA 810) Adding information on GTW-PC: Buffer overflow management configuration (CRA 758) Adding information on GTW-PC: Time stamp handling on SBUS (CRA 824) Adding information for use of MPS Datapoints in an ISagraf Automation Adding information for configuration of Substation mode dependency Adding information on OI Printers state
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 4 / 173
C
30/07/07
G. JUVANON
Delivery of C264 VB4.54B, EQ_SIM V1.6.4, GTW V4.22.8, OI G.03.06A with SCADA 2000 M4RC62A, SCE V4.46, SBUS Agency V4.4 and SMT K.00.04
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.
Adding procedure to replace a new tztab file into the SCE Adding procedure to restore C264 boot parameters Adding information on DB9 connection on CPU260 Adding information on C264: Datapoints association (CRA 717) Adding information on GTW-PC & C264-GTW: Buffer overflow management configuration (CRA 758) Adding information on Datamodel optimisation configuration (CRA 801) Adding information on V35 boards at 64Kbauds on PACIS gateway (CRA 783) Adding information on new symbols for Ctrl MultiState, new columns and new button in tools bar for Viewer, OI memo bitmaps configuration, control pop-up configuration, Adding information on CDCII protocol configuration (DPC & SPC Datapoints) Adding information on Network configuration for PACiS OI/SMT on Windows XP § 8.2
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 5 / 173
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.
TABLE OF CONTENTS 1.
GENERAL .....................................................................................................................................................8
2.
OPERATOR INTERFACE..........................................................................................................................9
2.1 OI INSTALLATION ........................................................................................................................................9 2.2 STAND-ALONE OI CLIENT INSTALLATION ..................................................................................................11 2.3 SQL SERVER 2005 STANDARD EDITION INSTALLATION ............................................................................16 2.3.1 Microsoft SQL Server 2005 Installation...............................................................................................16 2.3.2 Making SQL Server 2005 Compatible with PACiS OI .........................................................................31 2.4 SETTINGS FOR DCOM ...............................................................................................................................44 3.
PACIS WATCH ..........................................................................................................................................47
4.
SYSTEM MANAGEMENT TOOL ...........................................................................................................50
5.
SYSTEM CONFIGURATION EDITOR ..................................................................................................52
6.
COMPUTER C264......................................................................................................................................54
6.1 6.2
COMPUTER INSTALLATION.........................................................................................................................54 RUSSIAN LANGUAGE CONFIGURATION .......................................................................................................55
7.
GATEWAY..................................................................................................................................................60
8.
STATION BUS AGENCY ..........................................................................................................................61
8.1 8.2 9.
INSTALLATION ...........................................................................................................................................61 USE SBUS AGENCY FILE AS DLL ...............................................................................................................65 TUNNELLING MODE...............................................................................................................................67
9.1 TUNNELLING MODE THROUGH SERIAL PORT ..............................................................................................67 9.2 TUNNELLING MODE THROUGH ETHERNET NETWORK .................................................................................68 9.2.1 Installation of tunnelling components...................................................................................................69 9.2.2 Launch the tunnelling ...........................................................................................................................70 10.
CONFIGURABLE REPORTS CREATION........................................................................................71
10.1 10.2
REPORT TEMPLATE CREATION USING CRYSTAL REPORT............................................................................71 REPORT LAUNCHING BUTTON CREATION USING THE SCE ..........................................................................81
11.
CONFIGURATION INFORMATION .................................................................................................83
11.1 SCE CONFIGURATION................................................................................................................................83 11.1 OI PRINTER CONFIGURATION ..................................................................................................................107 11.1.1 OI Printer : Marked characters .....................................................................................................107 11.1.2 Printing spooler configuration.......................................................................................................107 11.2 COMPUTER PRINTER CONFIGURATION.....................................................................................................108 11.3 TIME CONFIGURATION .............................................................................................................................108 12.
ISAGRAF AUTOMATION .................................................................................................................110
12.1 12.2
SCE: MULTI DO IN THE SAME STEP .........................................................................................................110 USE OF MPS DATAPOINTS .......................................................................................................................112
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 6 / 173
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.
13.
OI PRINTER STATES.........................................................................................................................113
14.
OI TWIN SERVER SAFE FUNCTION .............................................................................................114
14.1 SPECIFICATION ........................................................................................................................................114 14.2 CONFIGURATION AND SETTINGS ..............................................................................................................115 14.2.1 SCE Configuration .........................................................................................................................115 14.2.2 Setting Twin Server Safe ................................................................................................................115 14.2.3 Modify files for Twin servers safe function ....................................................................................116 14.2.4 Setting registry key for Twin servers safe function.........................................................................118 14.2.5 PACiS OI Client – connection to servers .......................................................................................118 14.3 FAILURE CASES ........................................................................................................................................119 14.3.1 Loss of Master PC ..........................................................................................................................119 14.3.2 Loss of Remote PC .........................................................................................................................120 14.3.3 Backup Historian Data Base..........................................................................................................120 14.3.4 Restore Historian Data Base..........................................................................................................120 14.3.5 Copy Historian backup file ............................................................................................................121 14.3.6 Copy Persistence files ....................................................................................................................121 15.
IEC61850 / IEC61850 GATEWAY .....................................................................................................122
15.1 15.2
"LOWER" NETWORK.................................................................................................................................123 "UPPER" NETWORK ..................................................................................................................................126
16.
ARCHIVE TRENDVIEWER ON STANDALONE PACIS OI CLIENT ........................................130
17.
WINDOWS XP .....................................................................................................................................133
17.1 SCE .........................................................................................................................................................134 17.2 OI/SMT & GATEWAY ..........................................................................................................................135 17.2.1 Deactivation of Security Center .....................................................................................................135 17.2.2 Deactivation of Firewall ................................................................................................................137 17.2.3 Settings for DCOM.........................................................................................................................138 17.2.4 Folders options...............................................................................................................................144 17.2.5 Shared Folders ...............................................................................................................................144 18.
TREND VIEWER REAL TIME .........................................................................................................152
18.1 OVERVIEW ...............................................................................................................................................152 18.2 RUN-TIME MODE DISPLAY .......................................................................................................................153 18.2.1 Trend Real-Time mode ...................................................................................................................153 18.2.2 Trend Pause mode..........................................................................................................................154 18.2.3 Using the Toolbar ..........................................................................................................................154 18.2.4 Using the Cursor ............................................................................................................................156 18.2.5 Using the Scrollbar ........................................................................................................................158 18.2.6 Using the Toolbox ..........................................................................................................................159 19.
PIX CUBICLE TEMPLATE ...............................................................................................................161
19.1 SCOPE ......................................................................................................................................................161 19.2 TEMPLATE COMPOSITION ........................................................................................................................161 19.2.1 Automatisms ...................................................................................................................................161 19.2.2 Detailed description of the different automatisms..........................................................................162 19.2.3 Description of the data points in relation with the specifications ..................................................170 19.3 HOW TO USE THE PIX TEMPLATE ............................................................................................................171 19.3.1 Use of the PIX Template at the SCE level ......................................................................................171 19.3.2 Configure the parameters of the PlX..............................................................................................172
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 7 / 173
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.
1. GENERAL This document gives simplified indications to install and to configure PACiS V4.4 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 PCs of the application. Operating System: • •
Windows 2000 SP4 Windows XP SP2
If you install SCE, OI or Gateway on Windows XP Operating System, the §17 describes the specific actions on Windows XP. Remark : The Equipment Simulator must be installed on a dedicated PC (i.e. it cannot be installed with another PACiS application like SMT). SMT must not be installed on the same PC as the GTW. The PC which supports PACiS OI must not have "HMI" as Network name.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 8 / 173
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. OPERATOR INTERFACE In "OI G.03.06A" 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_RC62A folder which contains the SCADA 2000 application (S2K M4 RC62A)
•
the SNTP folder which contains files to easily configure a SNTP client
•
the Twin Server Safe Settings folder which contains files to define the setting for the Twin Server Safe function (refer to § 14)
2.1 OI 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 2000 is installed or if SQL Server 2005 is installed (see information § 2.3) – If no, install it – If yes, delete the "Historian" database 2. If a previous version of OI application is installed, uninstall it 3. If a previous version of SCADA 2000 application is installed, uninstall it 4. If OI and/or SCADA 2000 applications have been uninstalled, reboot the PC 5. Backup the Historian Database, delete it and Recreate it by using "Microsoft SQL server Entreprise Manager" or "Microsoft SQL Server Management Studio") 6. Launch S2K M4RC62A\M4RC62A_setup.exe to install SCADA 2000 application (custom installation, don't change the default path of the installation (C:\Program Files\USDATA)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 9 / 173
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. Reboot the PC 8. Launch PROGRAMS\PACiS OI\setup.exe to install the OI application 9. Reboot the PC Notes: • check the msxml.dll file dates in C:/WINNT/system32 or in 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 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 dll files. Rename the current files (from msxml.dll to msxml.dll__), then copy the new dll files from zip file.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 10 / 173
2.2 Stand-alone OI client 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.
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 OI installation, use the “autologon” box to define on which OI server the client will be connected
2. Be sure to define the same Windows user with the rights on each PC, and log-on the PC with this user
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 11 / 173
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.
3. 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,
•
Give "SharedWorspace" as name
4. Active the SNTP client integrated in Windows 2000 or in Windows XP: Two directories: one for Windows 2000 and one for windows XP •
open the w32time_parameters_one_server.reg file if only one server is master clock or w32time_parameters_two_servers.reg file if two servers are master clock to modify the NtpServer parameters (IP address of the SNTP servers, i.e. the computers defined as SNTP server in the configuration)
•
launch the w32time_parameters_one_server.reg w32time_parameters_two_servers.reg to update the Windows registry
•
put the w32time.cmd file (available in both SNTP folders) in the startup folder of the PC which supports the stand-alone OI client
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
or
Identification Number: 2059660 Page: 12 / 173
5. Configuration of network disconnection/ reconnection mechanism:
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 order to improve client disconnection/reconnection scheme, a new mechanism has benne added to PACiS OI client software. This mechanism has to be activated only for standalone PACiS OI Client, and it can be deactivated if required. If this mechanism is configured, the SMT must not be install on the same PC as standalone PACiS OI Client. To configure that feature, you have to set two values un the registry. These values are located under the following "HKEY_LOCAL_MACHINE/SOFTWARE/AREVA/PACIS/Configuration".
key:
Value Name
Value Type
Default Value
Comment
NetworkLinkReset
REG_DWORD
0
0: the function is NOT activated 1: the function is activated
NetworkLinkName REG_SZ
Local Area Connection
Name of the network link to reset on OIServer failure, if the function is activated
How to set the "NetworkLinkName" value: This value has te set according the name of the network link used for PACiS OI Client/PACiS OI Server connection. The link name can be found with the 'Windows explorer', by clicking on the properties of the "My Network places" item.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 13 / 173
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.
If the name of this connection changes, the "NetworkLinkName" has to be changed too. 6. Use of PACiS OI Client Watch : For PACiS OI Client standalone, it's better to use the shortcut "PACiS OI Client Watch".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 14 / 173
2.3 SQL Server 2000: 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.
Now, Microsoft SQL server Agent must be running on PACIS OI. So if not running, you have to start it. •
Open SQL Service Manager from "icon tray" in the task bar
a. Launch "SQL Server Agent" by clicking on "Start/Continue"
b. Configure "SQL Agent Service" for an automatic start at the start of the system by tagging "Auto-start service when OS starts"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 15 / 173
2.4 SQL Server 2005 Standard Edition 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.
2.4.1 Microsoft SQL Server 2005 Installation REMARK : Before installing SQL SERVER 2005, the former server version(SQL SERVER 2000) must be uninstalled. It can be uninstalled via the Windows Control panel: "Add/Remove Programs" item.
This software is installed via an Installation software. Insert the "Microsoft SQL Server 2005 Standard Edition" CD-ROM (autorun execute). The following message appears briefly,
followed by this one:
Click on " Server components, tools, Books Online, and samples". AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 16 / 173
Remark : If the following message appears, you have to install "Microsoft Windows Installer 3.1". The Internet address given in the message box is no longer in use. You should instead try the following one :
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.
[http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838de776fd4138c&DisplayLang=en] If the above link fails, try to download from the Microsoft Download Center.
Normally, the following End User Licence Agreement (EULA) screen appears:
Check "I accept the licensing terms and conditions" and click on the "Next". AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 17 / 173
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.
SQL Server 2005 now inspects your PC and prepares a list of any prerequisites it needs prior to installation.
When the list is prepared, click either on "Install" or "Next". When all prerequisites are installed, SQL Server 2005 displays the following screen:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 18 / 173
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.
Now SQL will check your system configuration:
Let the system configuration check complete. Now SQL Server 2005 shows you a "Welcome" screen. Click on "Next".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 19 / 173
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 20 / 173
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.
This screen should show 0 errors, 0 Warnings and a "Success" status. If there is a Warning like in the example below, you probably need to install additional Services:
Here, the user clicked on "messages" to get additional information. "Windows IIS component" must be installed.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 21 / 173
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 order to install the "Internet Information Services" component (IIS), select the "Add/Remove Programs" icon in the Windows Control Panel., then select the "Add/Remove Windows components". To install IIS, check the checkbox relative to IIS and click "Next". You may need to insert the Windows 2000 or Windows XP installation disk to be able to move on. You can get another warnings. For "Internet Explorer Requirement", please install Internet Explorer 6.0. For "MDAC (Microsoft Data Access) Version Requirement', please install Microsoft Data Access Version 2.8.
[http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037185d0506396c&DisplayLang=en] Remark : If the above link fails, try to download from the Microsoft Download Center
Normally, there was no errors nor warnings displayed in the "System Configuration Check" screen. Please proceed by clicking on "Next".
The Server Install Wizard prepares itself with the following screen and prepares for registration as follows: Type-in "AREVA" as Name and Company and enter the numbers written on the SQL Server 2005 Installation CD to complete registration. Then click on "Next":
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 22 / 173
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 "Next". The next screen lets you select the components to install with SQL Server 2005. Please select the following items: •
SQL Server Database Services
•
Analysis Services
•
Notification Services
•
Integration Services
•
Workstation Components, Books Online and development tools
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 23 / 173
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.
Then click "Next".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 24 / 173
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 “Default instance” then click “Next”
Select the option "Use the built-in System account" and choose "Local system" from the corresponding listbox. Check SQL Server, Analysis Services and SQL Browser. Click on "Next". AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 25 / 173
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 "Authentication Mode" screen, check the "Mixed Mode" option. You need here to define a temporary password that will be erased later on, for instance "AREVA2006". Click on "Next".
Check "SQL collations" and select "Dictionary order, case-insensitive, for use with 1252 Character Set" (as shown), then click on "Next". AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 26 / 173
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.
Leave default settings as they are, no check options and click on "Next".
Now here is the "Ready to Install" screen. SQL Server 2005 is now ready. Please click on "Install". Several screens will show as follows:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 27 / 173
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 28 / 173
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.
When the "Next" button is ungrayed, click on "Next".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 29 / 173
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.
After a few minutes, it is proposed to end the installation by clicking on the "Finish" button.
Click on "Finish" then reboot the PC.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 30 / 173
2.4.2 Making SQL Server 2005 Compatible with PACiS 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.
2.4.2.1 Creation of a blank password First open the "SQL Server Management Studio" program by following the link shown below:
Type in the server name (computer name of the PACiS OI Server) : Then click on "Connect":
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 31 / 173
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 left panel of the Microsoft SQL Server Management Studio screen, do :
Double-click on the "Security" folder to open it
Double-click on the "Logins"” folder to open it
Right-click on "sa" and select "Properties"
In the following screen, you MUST erase the former password ("AREVA2006") given during the SQL Server 2005 installation.
In order to obtain this result, do the following:
Erase the password in the "Password" area.
Erase the password in the "Confirm Password" area.
UNCHECK the "Enforce password policy" checkmark.
Click "OK".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 32 / 173
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.
You then get the following confirmation message:
Click on "Yes". Then Exit from SQL Server Management Studio
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 33 / 173
2.4.2.2 Creation of Historian DataBase
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.
First open the "SQL Server Management Studio" application and connect to the SQL server as shown in the previous paragraph. Please now right-click on the "Databases" folder and select "New database…" from the contextual menu.
Enter Historian (be careful to the case) as the database Name, and click on the "…" button to change "Autogrowth". AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 34 / 173
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.
Check "Enable Autogrowth": the data files automatically increase in size by the amount indicated in the following options (megabytes or percent): select the "In Percent" option and type in 20 (percent). Select "Restrict file growth (MB)" and specify the size in Mbytes to which a restricted data file can grow to 10000. Click on OK to validate and create the database. The following screen shows the newly created "Historian" database with the correct "Autogrowth" parameters.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 35 / 173
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 "OK" and quit the "SQL Server Management Studio".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 36 / 173
2.4.2.3 Connexion to the Historian DataBase
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 Start>Settings>Control Panel>Administrative Tools>Data Source
Click on the "System DSN" tab and then select "SQL Server" from the list to create a new Data Source. Click on "Finish".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 37 / 173
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.
Type Historian in the Name field and in the Description field. In the Server list, choose or type the server name (for example "OWSM"”) and click on "Next" .
Accept the default and click on "Next".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 38 / 173
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.
Check the "Change the default database to" checkbox and select "Historian" from the dropdown list. Then click on "Next".
Accept the default and click on "Finish".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 39 / 173
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 "Test data Source".
After the message "TESTS COMPLETED SUCCESSFULLY" has been displayed, click on "OK". To close the ODBC data source windows, click on "OK" on each window.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 40 / 173
2.5 SQL Server 2005 : 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 authorization.
Now, 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
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:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 41 / 173
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:
•
Select the Service Tag and put the Start mode to Automatic:
Click on Apply and on OK AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 42 / 173
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.
• Check the state and the Start Mode of SQL Server Agent:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 43 / 173
2.6 Settings for DCOM: Windows 2000
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.
Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to configure permissions.
Go to Default Properties Tab, and set "Default Authentication Level" to "(None)" as below:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 44 / 173
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.
Go to Default Security Tab, and set "Default Configuration Permissions" to "Full Control":
Go to Default Security Tab, and set "Default Access Permissions" to "Allow Access" for "Administrators" and "Everyone":
Go to Default Security Tab, and set "Default Launch Permissions" to "Allow Launch" for "Administrators" and "Everyone":
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 45 / 173
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.
Go to "Application" Tab, search for "S2K.OpcServer" application, select it and click on "Properties", set "Authentication Level" to "(None)":
Do the same for "SCADA 2000 CS2K.AlarmServer" application.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 46 / 173
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.
3. PACIS WATCH In "P_WATCH V2.6" folder you will find : •
the LICENCE_CONTRACT folder which contains the software licencing text
•
the PRODUCT_INFORMATION folder which contains the User Manual (draft)
•
the PROGRAMS folder with the application (PACiSWatchSetup.exe)
The installation of PACiS Watch is mandatory on both PC in case of OI redundancy use.
Launch PACiSWatchSetup.exe to install the PACiS Watch application. Note : this release is now installed in AREVA folder 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. The installation procedure launches the registration of PacisWatch as standard executable (called also « local server »). At the end of installation the following information message box is displayed: AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 47 / 173
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 case of "Yes" response, PacisWatch is launched using the initialisation file present in the installation directory. If a new release (higher than 2.0) of PACiS Watch is to install, it is recommended to install it directly, without unsinstalling the previous one, otherwise, the eventual modifications done in the .ini file will be lost.
Uninstallation of release V2.0: 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 uninstallation. “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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 48 / 173
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 49 / 173
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.
4. SYSTEM MANAGEMENT TOOL In "SMT K.00.04" folder you will find the SMT application. Don't install SMT on the same PC as GTW. 1. If a previous version of SMT application is installed, uninstall it 2. Launch SMT-R3_K.00.04.exeto install SMT application 3. Reboot the PC 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 an 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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 50 / 173
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.
Change the line DisturbanceConvertersPath=C:\Program 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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 51 / 173
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. SYSTEM CONFIGURATION EDITOR In "SCE V4. 46" folder you will find : •
the SCE_4.46.installer.exe file which allows the SCE application installation
1. If a previous version of SCE application is installed, uninstall it 2. Launch SCE_4.46.installer.exe 3. If a previous version of OI parser application is installed, uninstall it 4. Launch PROGRAMS\XML Parser\setup.exe (in OI G.03.06A folder) If the SCE is not installed on the same PC as PACiS OI, do the followings: 5. If a previous version of SCADA 2000 is installed, uninstall it 6. Launch S2K M4RC62A\M4RC62A_setup.exe (in OI G.03.06A folder) to install only Client Builder application 7. 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 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 dll files. Rename the current files (from msxml.dll to msxml.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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 52 / 173
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.
•
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 : • 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=F9DFA82C9A3B-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).
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 53 / 173
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. COMPUTER C264 In "C264 VB4.54B” folder you will find : •
the Computer_B4.54B.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 "boot rom" program
6.1 Computer installation Launch Computer_B4.54B.exe.
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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 54 / 173
6.2 Russian / Chinese language 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 authorization.
If the installed Windows 2000 is not Russian or Chinese, it's proposing you to choose the language used by the PC. The selected language is saved in Registry. For non-occidental languages: Russian (cyrillic) or Chinese, the PC have to be configured to support Cyrillic or simplified Chinese fonts. This modification is mandatory to use CMT for such languages. From the program "Start\Parameters\Configuration Panel\Regional Options"
From "Language setting for the system" click on "Set default…" button. A new window will open and you select Russian for Russian or Chinese (Popular Chinese Republic) for simplified Chinese.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 55 / 173
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 upper part of ASCII table (128 to 256) will now point to specific characters of Cyrillic or simplified Chinese alphabet. Reboot the PC to apply these changes.
6.3 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 A Personal Computer is needed. Any Windows operating system can be used. The PC hardware requirement is:
• COM port in RS232C (setting) • 100 Mo of free space on hard disk The PC software's needed is:
• Serial COM terminal (TeraTerm, HyperTerminal…)
for Boot Setting
The Serial COM terminal is configured for serial communication with:
• TTY mode • 19200 Baud/s • 8 bits no parity 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. AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 56 / 173
DB 9 5
1
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.
DB 9 5
6
9
Computer MiCOM C264C
1 2 3 4 5 6 7 8 9
1 2 3 4 5 6 7 8 9
9
1
6 PC serial PORT
OR 1 2 3 4 5 6 7 8 9
1 2 3 4 5 6 7 8 9
C0076ENa
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:
“boot device “processor number “host name “file name “inet on ethernet “inet on backplane “host inet “gateway inet “user AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
: tffs=0,0 :0 : : /flash/bin/vxWorks : : CR : : 0.0.0.0 : Identification Number: 2059660 Page: 57 / 173
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.
“ftp password “flags “target name “startup script “other
: : 0x0 : : : motfec
[VxWorks Boot]:
Settings to enter The settings to enter are: -
•
factory host PC name: your maintenance laptop network name
•
factory host IP address: your maintenance laptop IP@
•
factory target name: should be the Computer name defined by SCE for its database
•
factory C264 IP address: should be the Computer IP address defined by SCE for its database
•
user name and ftp password: FTP user name, defined for the FTP server - it is good practice to keep factory setting and to define on the PC user c264_cpu2 or c264_cpu3 according to your CPU type with the password vxWorks
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:
“boot device “processor number “host name “file name AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
: tffs=0,0 :0 : : /flash/bin/vxWorks
CR CR CR Identification Number: 2059660 Page: 58 / 173
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.
“inet on ethernet “inet on backplane “host inet “gateway inet “user “ftp password “flags “target name “startup script “other
: CR : CR : CR : 0.0.0.0 CR : CR : CR : 0x0 CR : CR : CR : motfec CR
[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.4 C264 connection 6.4.1 Connection CPU260 The DB9 connectors description: 1
CD
2
RX
3
TX
4
5V ( for ECU20x supply)
5
ground
6
Not used
7
RTS
8
CTS
9
Not used
Note: unlike standardized RS232 connector, pin 4 is not normally used as the DTR signal (Data Terminal ready). It is here permanently connected to power supply +5 V. So this pin 4 must not be used in a null-modem cable.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 59 / 173
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. GATEWAY In "GTW V4.22.8" folder you will find : •
the GTW_4.22.8.exe file which allows the gateway application installation
•
the GI74 folder which contains installation documentation (draft)
•
the OPC-client folder which serversurclientopc.exe files
contains
clientopc_1.1.exe
&
Don't install the GTW on the same PC as SMT. 1. Install the OSILLC driver (provided with the Station Bus agency application) 2. If a previous version of gateway application is installed, uninstall it 3. Launch GTW_4.22.8.exe to install gateway application 4. Install SBUS Agency V4.4 5. Reboot the PC
Note for 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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 60 / 173
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. STATION BUS AGENCY
8.1 Installation In "SBUS V4.4" folder you will find : •
the Agency_V4.4.exe file which allows the Station Bus application installation
1. Uninstall the previous agency 2. Launch Agency_V4.4.exe to install the Station Bus application as described below
In the “License agreement” window, click on “I accept the agreement”, then on “next”
Then in the "Select Destination Directory", define the installation folder and click on "next" (the default installation folder is C:\Program Files\Areva\PACIS)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 61 / 173
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 (all by default)
In the "Select Start Menu Folder" window, select where the shortcut to launch the Agency will be available (in PACiS folder by default) AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 62 / 173
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.
Then click on "next" then on “install” to install the components.
3. Follow description of installation manual to install OSILLC driver 4. Reboot the PC Note1: The agency must be installed on each PC which supports the OI server, the SMT, and the gateway. Note2: During installation, Dr Watson is enabled and configured with specific parameters; if another 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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 63 / 173
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.
VisualNotification = 0
Auto = 1 Debugger = drwtsn32 –p %Id –e %Id -g
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 64 / 173
8.2 Use SBUS Agency file as 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 authorization.
SBUS Agency file for SMT and OI is used as dll. There is no more icon of the Agency in the system tray. Each sub-system runs each own Agency dll. So the user must not launch Win32Agency.exe. 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
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 AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 65 / 173
The agency.log file is in the following directory: -
For SMT :
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.
C:\Program files\AREVA\PACiS\Smt\SBUS -
For OI: 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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 66 / 173
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.
9. TUNNELLING MODE 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
9.1 Tunnelling mode through serial port Computer front port Hyper-terminal 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 :
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
•
TunnelingRSState allows to know if the tunnelling function is used
•
TunRSLines gives on which legacy ports a tunnel can be opened Identification Number: 2059660 Page: 67 / 173
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.
•
TunRSIed gives the list of connected IED on the line and their address
•
TunRSStart , allows to open a tunnel between the PC and the IED
•
TunRSStop allows to close the tunnel
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.
9.2 Tunnelling mode through Ethernet network • • •
PatuSpy software UCA2 agency MiCOM S1
Ethernet network (UCA2) C264
tunnel Legacy port (Modbus or T103)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
IED
Identification Number: 2059660 Page: 68 / 173
9.2.1 Installation of tunnelling components
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.
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 \Tunneling folder) 3. Launch PATDbWin and set your parameters (Edit menu). Then close PATDbWin.
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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 69 / 173
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. 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&R103 and rename it W32KommDll.dll
9.2.2 Launch the tunnelling 1. Launch the LaunchS1V2Patu.exe file
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”
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 70 / 173
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. CONFIGURABLE REPORTS CREATION Configurable reports are created in two steps : •
Report template creation using Crystal Report
•
Report launching button creation using the SCE
Note on Crystal Report: Crystal Report doesn't support "/" and "\" characters: if used, the report will be empty.
10.1 Report template creation using Crystal Report Crystal Report must be installed on a PC which supports also the OI. The PACiS database (which contains configuration of archived information, mean values, …) must be downloaded in the OI. The OI must be launched at least one time to initialise the SQL tables.
1. Launch Crystal Report 2. Select using the Report Expert option to create a new report template and click OK
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 71 / 173
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.
3. Select Standard report and click OK
4. Click on Database button
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 72 / 173
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. Select More Data Sources, then Microsoft SQL Server
6. Gives the server name (pacisoi9 in the example), the user ID (always sa) and select the Historian database. Click OK
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 73 / 173
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. The list of available SQL tables appears in More Data Sources\Microsoft SQL Server\ folder
Select required table(s) and click on Add. When all required tables have been added, click on Close
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 74 / 173
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.
Useful tables for measurements mean values : S2KAnnual_VTQTimeTable
Contains the last 60 monthly (i.e. 5 years) characteristic value of measurements (mean, max and min values)
S2KMonthly_VTQTimeTable
Contains the last 430 daily (i.e. 15 months) characteristic value of measurements (mean, max and min values)
S2KDaily_VTQTimeTable
Contains the last 35 days archives of measurement mean values
S2KVTQDictionary_Table
Contains the label, the origin and the type (mean, max, min) of each archived measurements. This table is compulsory when using the Annual, Monthly and/or Daily tables
Useful tables for events : S2KEventGroup_Table
Contains the origin label of the events
S2KEventMsg_Table
Contains the label, the date and the states of each events
These 2 tables must be used when creating an event report template.
The following items gives information concerning report template creation based on monthly archived mean values.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 75 / 173
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. After selecting S2KMonthly_VTQTimeTable and S2KVTQDictionnary_Table tables, the following window appears :
Click on Next>>
9. Select the field(s) to display in the report and click on Add->. Then click on Next>>
The “Column Heading” is used to give a column name for each field.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 76 / 173
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.
Useful fields for S2KAnnual_VTQTimeTable, S2KDaily_VTQTimeTable tables :
S2KMonthly_VTQTimeTable,
OBJID
Measurement cross-reference in the S2KVTQDictionary_Table
OBJVALUE
Measurement value
OBJFILETIME
Measurement time stamping. Must be used with the following formula : FiletimeToString2({S2Kxxxx_VTQTimeTable.OBJID},{S2Kxxxx_VT QTimeTable.OBJFILETIME},” “,”hh:mm:ss.tt”)
Useful fields for S2KVTQDictionary_Table : OBJID
Measurement cross-reference in the S2KxxxxxVTQTimeTable
OBJPROPNAME
Property of the archived measurement : AverageCycle for the mean value PeakMinCycle for the minimal value - PeakMaxCycle for the maximal value
TABLENAME
Name of the table in which the measurement is archived
OBJNAME
Measurement label
OBJAREANAME
Origin label of the measurement
Useful fields for S2KEventMsg_Table : ObjectNameText
Event label
EventFileTime
Event time stamping. Must be used with the following formula : FiletimeToString2({S2KEventMsg_Table.Loc aleID},{S2KEventMsg_Table.EventFileTime}, ” “,”hh:mm:ss.tt”)
EventMsgText
Event state
AreaGroupID
Event cross-reference in the S2KEventGroup_Table
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 77 / 173
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.
Useful fields for S2KEventGroup_Table : GroupID
Event cross-reference in the S2KEventMsg_Table
GroupPathName
Origin label of the event
10. The group page allows to group values depending on sort rules and to apply calculation on these group values (optional)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 78 / 173
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.
11. The chart page allows to display data on chart form (optional)
12. The select page allows to select a subset of information to display (optional)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 79 / 173
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.
13. The style page allows to select a style for the report (optional)
14. Click on Finish : a preview is displayed
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 80 / 173
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 Design table allows to modify the template as you want. Refer to the Crystal Report documentation to be able to use all features. The report template must be saved using an authorised name (see § 11.2).
In Design mode, add in the Report Header a text object “TYPE=HISTORICAL”. Without this object, the report cannot be used.
10.2 Report launching button creation using the SCE
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 81 / 173
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.
Create a Run Application object attached to a graphical object. The Application name attribute must be one of the following names : Report1, Report2, Report3, Report4, Report5, Report6, Report7, Report8, Report9 or Report10 (respect lower and upper cases !). No other names are allowed. This name corresponds to the template file (.rpt file) created with Crystal Report. Copy the used .rpt files in the XML Parser folder S2K_HMI\Reports\ (ENU for English, FRA for French).
On the OI, when clicking on the configured report button, a .xls file (Excel format) is created in the folder “Program Files\USDATA\S2K\Reports\Exported”. The file name is structured as follows : __.xls (for example, report1_01_07_2005_13_56_43.xls for a report issued from repor1 template, writing the 7th of January 2005 at 13:56:43).
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 82 / 173
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.
11. CONFIGURATION INFORMATION
11.1 SCE Configuration 1) Measurement format The # cannot be used in decimal format, only 0 is allowed.
2) OI: Alarm Viewer : Alarms list The datapoint state on all alarm lists can be “current state” or “alarm state”. The attribute “display of datapoint state” has to be set respectively to “current state” or “alarm state”.
3) DPC datapoint An interlock violation SPS can be attached to a DPC datapoint. When the command of the DPC is negative because of an interlocking violation, this SPS is set to 1.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 83 / 173
4) C264 GTW / GTW PC T101 : ASDU 18 & ASDU 19
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.
Twp MPS system Datapoints have been added under Master T103 IED : PSE and PCO info. These datapoints can be linked to a SCADA T101 MPS address (ASDU 18 & 19).
5) C264 Legacy Bus T103: Quality substituted transmitted during GI An attribute "substituted if unknown" (YES/NO) has been added for each MV address:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 84 / 173
6) Cyclic SPS In a C264, up to 8 transient SPS can be defined as cyclic (day cycle). The user must configure for each the trigger time (hour and minute).
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.
These SPS can be used to activate a periodic treatment into the C264.
7) Global Alarm Acknowledgement A SPS "Global Alarm Ack" can be used to automatically acknowledge the new alarms into the C264 and also into the OI. On the SCE, the Substation SPS Electrical Datapoint "Global Alarm Ack" has to be added on the substation level. This activation mode of this SPS must be defined as permanent or "permanent with computer auto-reset" for the treatment by the OI. This SPS may be any wired SPS or SPS activated by a Control (use of "Global alm ack ctrl") from the SCADA or generated by any PSL. It is also possible to launch a global Alarm acknowledgement at a fixed time by using a cyclic SPS, see below.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 85 / 173
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.
To stop the possibility of automatic acknowledgement, a PSL can be used as follow: 1st possibility;
FBD SPS1: SPS Permanent : Selection for authorized or not the auto-Alarm-Ack function, this SPS can be managed through a SPC from OI or SCADA, or wired on DIU FBD cySYS: Cyclic SPS ("Day cyclic SPS") to automatically acknowledge the alarm at a fixed time FBD output: Output of PSL linked to the "Global Alarm Ack", SPS "Permanent" After the authorization by "FBD SPS1" ("AND"), the "FBD cySPS" is converted into a pulse of 10 ms (min) by "RS" and "TON".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 86 / 173
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.
2nd possibility;
FBD SPS1: SPS Permanent : Selection for authorized or not the auto-Alarm-Ack function, this SPS can be managed through a SPC from OI or SCADA, or wired on DIU FBD cySYS: Cyclic SPS ("Day cyclic SPS") to automatically acknowledge the alarm at a fixed time FBD output: Output of PSL linked to the "Global Alarm Ack", SPS "Permanent with computer auto-reset".
8) DPS, MPS, SPS profile: Using of all Interlock values in FBD Automation An interlock value (true / false / invalid) will be configurable in SCE for all status of SPS, DPS and MPS defined in profiles. This interlock value will be used for FBD automation / interlock equation calculation, whatever was the origin of the datapoint (local, goose, …). Only one interlock value can be configured on a per status basis: this means that the same interlock value will be used in all FBD / interlock equations in which the datapoint is configured. New "interlock value" have been added into DPS, SPS and MPS profile:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 87 / 173
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 88 / 173
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.
Modification in 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 authorization.
If your project use force and substitute functions, you have to verify after the upgrade of the configuration that values for theses attributes are correct. The best solution to do this verification and to make modifications is to use the Query tool of the SCE.
In this example, you can quickly compare value of Reset and value of Forced Reset. If you want to retrieve the same configuration before this change request, these values must be the same. In this example, you have to modify the Forced and Substituted values for SPS profile 2 and 3.
9) DPS, SPS: Status check for command New item for "status check for command" attribute of the "has for feedback" relation: • •
Control authorized only if the device is in the opposite state, Control authorized only if the device is in the opposite state, jammed or undefined
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 89 / 173
10) SCE: Automatic Documentation for PSL A FBD export has been created. Te user can access to this function by clicking in tools\Export FBD 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 authorization.
A dialog box presents all FBD available on database and allows selecting all or part of them. The spare and template objects are not available.
The user has to define the output file, the FBD type to create (XML, MNG or PDF file) and also has to select which FBD he wants to export. The display of FBD can be based on Tree mode or List mode.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 90 / 173
11) SCE: Automatic Documentation for Wiring A wiring export has been created. The user can access to this function by clicking in tools\Export wiring 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 authorization.
A dialog box presents all Computers available and allows selecting all or part them. The spare and template objects are not available.
of
The user has to define the output file to be created (XML PDF file) and also has to select which Computer he wants to export. The display of Computers can be based on Tree mode or on List mode.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 91 / 173
12) SCE: Automatic Documentation for SCADA
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.
A SCADA export has been created. The user can access to this function by clicking in tools\Export Scada menu. A dialog box presents all Computers/Gateways available and allows selecting all or part of them. The spare and template objects are not available. The display of Computers/Gateways can be based on Tree mode or on List mode.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 92 / 173
13) GTW: AI Scaling
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.
New attributes have been added at SCADA MV address level: •
min value (default value = 0)
•
max value (default value = 0)
They are settable and taken into account during gateway data bag generation. If these attributes are equals (especially when using default value), their values are substituted by min scaled and max scaled values defined at associated MV level, during gateway data bag generation.
14) GTW & C264: T101 & T104 protocol: Buffer overflow management On GTW-PC SCADA protocol T101 and T104, 2 new attributes have been added under a new category "Buffer overflow": •
Buffer overflow support (Y/N), default No
•
Buffer overflow address (must be unique in all over the protocol)
On C264 SCADA protocol T101 and T104, 3 new attributes have been added under a new category "Buffer overflow": •
Buffer overflow support (Y/N), default No
•
Buffer overflow address (must be unique in all over the protocol)
•
Buffer overflow empty condition: Without emptying, Fifo full / SCADA (re)connection, Fifo full only
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 93 / 173
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.
15) GTW: Gateway ports : New protocol type: V35 ACKSYS-MCX •
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
On GTW-PC, a new board "V35 ACKSYS-MCX" has been added on Gateway port (attribute protocol type):
Identification Number: 2059660 Page: 94 / 173
16) GTW: CDC II Protocol: DPS & SPC 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 authorization.
A new attribute has been added at SCADA DPC Mapping level, SCADA execute order type: •
Select execute (default value)
•
Direct execute
17) Graphical mimic: Control MultiState: New symbols For a SBO sequence, four new states are added to this object : •
Open Selected, symbol "SelectOpen"
•
Close Selected, symbol "SelectClose"
•
Open Operate, symbol "OperateOpen"
•
Close Operate, symbol "OperateClose"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 95 / 173
18) Mimic: AlarmViewer and Events 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 authorization.
Alarm Viewer: New column "timestamp of last ack." This column contains the last alarm acknowledgement date. Events Viewer: New columns "originator category" and "originator identifier" The origin column content can be configurable from 68 char; ("full area name") to 17 char. ("short area name").
19) Printer: Printing formats: new columns New columns "originator category" and "originator identifier" and also the size of the "originator identifier" (from 8 to 33 characters):
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 96 / 173
20) Mimic: Control pop-up: Title & Automatic closure
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 control pop-up title can be defined in configuration. For a xPC configured under a module, it could be : •
•
Or
The default value is . For a xPC configured under a bay, the title is always . For a xPC configured upper a bay (i.e. at substation or voltage level), the title is always . A new SCE attribute, at control pop-up level, allows to define if the pop-up is automatically closed after the selection phase (for a SBO sequence) or not. The default value is “not automatically closed".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 97 / 173
21) Mimic: Viewers filtering management
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.
A new button, configurable for all viewers (alarms, states, events, archives), allows to: •
Indicate that a filter / sort action is on-going
•
Re-initialize all filtering / sorting criteria when clicking on this button
This button has 2 designs: Inactive indicator : no filtering nor sorting criteria are applied Active indicator : a filter or a sorting criteria is currently applied
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 98 / 173
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.
22) Mimic: Memo bitmaps configuration For selecting the bitmaps to be used for animating the different states of a memo, define a new bitmap under "Bitmap Tables" choosing as type: "Memo for OI Client". For each of the 4 states (initial, active, inactive, undefined), draw a new icon using the mimic editor or select if from a file. Then, it is necessary to set a "reference index" to the created bitmap (4 icons group) and to set the same index to the "Bitmap reference" of the memo that will use this bitmap.
Warning: Do not leave transparent areas when drawing memo icons using the mimic editor. Otherwise, these areas will be displayed in black color because the bitmap format itself does not support transparency. Therefore, it is advised to fill the memo icons background with the same color as the one used for the mimic.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 99 / 173
23) C264: DNP3 Slave: Unsolicited messages
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.
On DNP3 C264 SCADA protocol, 2 new attributes have been added •
Spontaneous message enabled (Y/N), default No
•
spontaneous (default value = 0)
24) GTW-PC: Time stamp handling on SBUS at connection On GTW-PC, a new attribute has been added: •
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
GTW timestamp at connection (Y/N), default No -
No: Current behavior, following a loss of communication with a Station Bus server, all datapoints attached to this server in the GTW becomes unknown, time-stamped with the date of the loss of communication,
-
Yes: At the re-connection of the server, the datapoints are timestamped with the re-connection date.
Identification Number: 2059660 Page: 100 / 173
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.
25) SCE: Tap Changer: Management of Higher/Lower Position & Goto min/max datapoints
These datapoints – Higher position, Lower position, Goto min/max - have to be managed by an Isagraf automaton as described below, if they are not wired on a Digital Input or Output board: -
For Higher position and Lower position Datapoints: If the Tap pos indicator is greater than the max position, then set to 1 the Higher position datapoint, If the Tap pos indicator is lower then the min position, then set to 1 the Lower Position datapoint. Otherwise set to 0 the Higher position and the Lower position datapoints
-
For Goto min/max Datapoint: This datapoint must be received by the IsaGraf automaton: -
If the new position is Min position, the automaton must send one or several commands to the transformer to decrease the current position until the transformer reaches the Min position,
-
If the new position is Max position, the automaton must send one or several command to the transformer to increase the current position until the transformer reaches the Max position.
Nota: this datapoint can be controlled by SCADA Gateway or PACiS OI.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 101 / 173
26) SCE: Substation mode dependency The HMI of definition of the attribute "substation mode dependency" has been modified as follows:
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.
SCE < V4.42:
SCE ≥ V4.42:
The user can choose if the command form SCADA is refused or accepted in case the substation is in Local mode, and if the command from OI is refused or accepted in case the substation is in Remote mode.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 102 / 173
27) C264: Datapoints Association
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 Datapoints Association function allows to create datapoints (called “target” datapoints) from other datapoints (called “original” datapoints), using the following rules: •
SPS to create a SPS (all status of the original SPS can produce a SET / RESET / INVALID status of the target SPS)
•
DPS to create a SPS (all status of the original DPS can produce a SET / RESET / INVALID status of the target SPS)
•
DPS to create a DPS (all status of the original DPS can produce a OPEN / CLOSED / JAMMED / UNDEFINED / INVALID status of the target DPS)
•
SPS to create a DPS (all status of the original SPS can produce a OPEN / CLOSED / JAMMED / UNDEFINED / INVALID status of the target DPS)
•
MPS to create a SPS (all status of the original MPS can produce a SET / RESET / INVALID status of the target SPS)
•
MV to create a SPS (all status of the original MV can produce a SET / RESET / INVALID status of the target SPS)
•
a status of the original datapoint can have no effect on the target datapoint (i ;e. : in configuration, the status of the original datapoint isn’t link to any status of the target datapoint)
This association is created in SCE configuration using a “is mapped on" relation between the 2 datapoints. The original datapoint can be issued from an other computer than the target datapoint. In this case, the states of the original datapoints are transmitted using GOOSE messages. For local datapoints, the non-filtered state is used for target datapoint calculation. All target datapoints are managed as other datapoints (transmission, use in automation, alarms, ….). Up to 10 "target" datapoints can be created from one "original" datapoint. Up to 100 datapoints can be defined as “original” datapoints. Mapping from SPS Datapoints to SPS Datapoints:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 103 / 173
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.
Mapping from SPS Datapoints to DPS Datapoints:
Mapping from DPS Datapoints to SPS Datapoints:
Mapping from DPS Datapoints to DPS Datapoints:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 104 / 173
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.
Mapping from MPS Datapoints to SPS Datapoints:
Mapping from MV Datapoints to SPS Datapoints:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 105 / 173
28) SCE: IEC61850 Datamodel optimisation
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.
On menu tools/options, a function has been added to generated optimized data model:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 106 / 173
11.1 OI Printer 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 authorization.
11.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 2491 printer. Refer to the printer manual to modify this code.
11.1.2 Printing spooler configuration Printing service uses Windows spooling primitives. There are some requirements on spooler configuration in order to ensure an optimize functionality: 1. 2.
Remote printers used in PACiS OI have to be declared in local spooler, 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,
− In “Advanced” tab, following options have to be selected: Always available, Priority 1, Spool print documents so program finishes printing faster Start printing immediately, Print spooled documents first, Enable advanced printing features.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 107 / 173
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.
11.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.
11.3 Time Configuration External Clock : UTC Time Zone : Country locale 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. AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 108 / 173
11.4 Integration of a new release of tztab 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.
In the SCE, the tztab file is in files\AREVA\PACiS\SCE\\data\cal'.
the
directory:
'C:\Program
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: Example: the line: 288:USA Central:UTC-6:-360:DST: -5 hours) 288S:0:2:8:14:3:0: Sunday at 2:00 288W:0:2:1:7:11:0: Sunday at 2:00
-6 hours (Local summer second March first
November
Can be replaced by: 288:USA Central:UTC-6:-360:DST: -5 hours) 288S:0:2:1:6:4:0: Sunday at 2:00 288W:0:2:25:31:10:0: Sunday at 2:00
-6 hours (Local summer first Avril last October
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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 109 / 173
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. ISAGRAF AUTOMATION
12.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).
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.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 110 / 173
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:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 111 / 173
12.2 Use of MPS 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 authorization.
The use of MPS Datapoints is particular:
The MPS values inside IsaGraf (via the debugger) are from 1 to 16, whereas in the C264, the values are from 0 to15.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 112 / 173
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.
13. OI PRINTER STATES 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 port 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:
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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 113 / 173
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.
14. OI TWIN SERVER SAFE FUNCTION
14.1 Specification The "Twin-Servers Safe" function aims to replace the "hot redundancy" OI function.
Architecture The principal OI Server is called "Master". The secondary OI Server is called "Remote". The OI Clients can be installed on the same PC than the OI Servers or on different PC. The OI Servers must be connected on different Ethernet switches.
Principle 1.
All OI Clients are, at the same time, connected to the same OI Server (the Master one by default). The operator has to verify the connected server in the OI Title Banner
2.
The 2 OI Servers receive in parallel information from Station Bus servers : the SQL historical database is updated independently on each server. Same management for datapoints current states and active / inactive alarms states
3.
The Master OI Server creates cyclically (every 5 mn) a persistence file, containing current alarms states, which is automatically copied on the Remote OI Server
4.
The Remote OI Server reads this persistence file and automatically updates the alarms states (regarding acknowledged / cleared states)
5.
Memos are shared between the 2 OI Servers
6.
Profiles and passwords are shared between the 2 OI Servers
7.
The OI Clients are simultaneously connected to the same OI Server, so controls can be issued from only one OI Server.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 114 / 173
14.2 Configuration and settings 14.2.1 SCE 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 authorization.
To define the Twin Server Safe function : 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
14.2.2 Setting Twin Server Safe 14.2.2.1 First Installation On both PCs, do the following actions (see below for details): 1) Copy "Twin Server Safe Settings" directory (in OI folder) to C:\ Twin Server Safe Settings 2) Create "C:\Backup" directory 3) Modify files (cmd, bat reg) for Twin server safe function 4) Set registry key 5) Start PACiS OI Server 6) Download Database from SMT 7) Switch Database from SMT 8) Start PACiS OI Client 9) When OI Client configuration is the good one, stop PACiS OI Client 10) Modify connection to servers 11) Start PACiS OI Client
14.2.2.2 New Database On both PCs, do the following actions (see below for details): 1)
Download Database from SMT
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 115 / 173
2) Switch Database from SMT 3) When OI Client configuration is the good one, stop PACiS OI 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 authorization.
4) Modify connection to servers 5) Start PACiS OI Client
14.2.3 Modify files for Twin servers safe function 14.2.3.1 On Master OI Server: •
"Master_key.reg" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\master_key.reg" Replace REMOTE by the PC name of the Remote OI Server Save file •
"Servers.dat" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\server.dat" Replace MASTER by the PC name of the Master OI Server Replace REMOTE by the PC name of the Remote OI Server Save file •
"Backup_historian.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\ backup_historian.cmd" Replace MASTER by the PC name of the Master OI Server Save file
•
"Restore_historian.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\ restore_historian.cmd" Replace MASTER by the PC name of the Master OI Server Save file AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 116 / 173
•
"Copy Historian backup to REMOTE.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy Historian backup to REMOTE.cmd "
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.
Replace REMOTE by the PC name of the Remote OI Server Save file •
"Copy persistence to REMOTE.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy persistence to REMOTE.cmd " Replace REMOTE by the PC name of the Remote OI Server Save file
14.2.3.2 On Remote OI Server: •
"Servers.dat" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\servers.dat" Replace MASTER by the PC name of the Master OI Server Replace REMOTE by the PC name of the Remote OI Server Save file •
"Backup_historian.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ backup_historian.cmd" Replace REMOTE by the PC name of the Remote OI Server Save file
•
"Restore_historian.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ restore_historian.cmd" Replace REMOTE by the PC name of the Remote OI Server Save file AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 117 / 173
•
"Copy Historian backup to MASTER.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy Historian backup to MASTER.cmd "
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.
Replace MASTER by the PC name of the Master OI Server Save file •
"Copy persistence to MASTER.cmd" file:
Edit (Notepad) file : "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy persistence to MASTER.cmd " Replace MASTER by the PC name of the Master OI Server Save file
14.2.4 Setting registry key for Twin servers safe function On Master OI Server : •
Execute "TWIN_SERVER_SAFE_FILES_FOR_MASTER\master.bat" file
On Remote OI Server : •
Execute "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\remote.bat" file
On PACiS OI Client Standalone : •
Copy "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\servers.bat" file to "C:\LocalWorkspace\Config files\" of the PACiS OI Client
14.2.5 PACiS OI Client – connection to servers The PACiS OI Client configuration has to be modify to notify that there are 2 possible servers (Master server and Remote server). The file "servers.dat" is provided in the PACiS delivery.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 118 / 173
On Master OI Server : •
Execute "TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy servers to LocalWorkspace.cmd" 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.
On Remote OI Server : •
Execute "TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy servers to LocalWorkspace.cmd" file
WARNING : the modification of the servers.dat file must be done after each download / switch of a database.
14.3 Failure cases 14.3.1 Loss of Master PC
N° Actions 1
Master PC
Remote PC
Restart
2
Backup Historian Database on Remote Server
3
Copy Historian backup file to Master Server
4
Copy persistence file from Remote Server to Master Server
5
Restore Historian Master Server
Database
on
6
Restart Master PACIS OI Server & PACiS OI Client
7
Stop PACiS OI Client
8
Start PACiS OI Client (the Client must be connected to Master OI Server)
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 119 / 173
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.
14.3.2 Loss of Remote PC
N° Actions
Master PC
Remote PC
1
Restart
2
Backup Historian Master Server
Database
on
3
Copy Historian backup file to Remote Server
4
Copy persistence file from Master Server to Remote Server
5
Restore Historian Database on Remote Server
6
Restart Remote PACIS OI Server & PACiS OI Client
14.3.3 Backup Historian Data Base Backup Historian Database on Remote Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ backup_historian.cmd" file
This procedure create a backup file into C:\BACKUP directory. Backup Historian Database on Master Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_MASTER\ backup_historian.cmd" file
This procedure create a backup file into C:\BACKUP directory.
14.3.4 Restore Historian Data Base Restore Historian Database on Remote Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ restore_historian.cmd" file
Restore Historian Database on Master Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_MASTER\ restore_historian.cmd" file
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 120 / 173
14.3.5 Copy Historian backup file Copy Historian backup file from Remote Server to Master 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.
•
Execute " TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy Historian backup to MASTER.cmd " file
Copy Historian backup file from Master Server to Remote Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy Historian backup to REMOTE.cmd " file
14.3.6 Copy Persistence files Copy Persistence files from Remote Server to Master Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy persistence to MASTER.cmd " file
Copy Persistence files from Master Server to Remote Server •
Execute " TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy persistence to REMOTE.cmd " file
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 121 / 173
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.
15. IEC61850 / IEC61850 GATEWAY The IEC61850 / IEC61850 gateway allows the connexion of 2 IEC61850 station bus network called below: "lower" and "upper" network. This chapter describes the process to define the configuration of the gateway on the lower network and the configuration of the gateway on the upper network.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 122 / 173
15.1 "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.
The actions describe below are the last actions the user have to process. It's assumed that the user has already build the configuration for this network. The name of the database: Energy_lower.mpc
CAUTION: Make sure that in this database, all the entity's names are unique, entity means substation, voltage level, bay, module, datapoint, IEC physical device. 1 - Open this database, add a gateway. Enter the name and the TCP/IP address of this gateway on the lower network, in example: GTW_IEC, 10.10.1.20.
2 – Add an IEC61850 protocol scada network under this gateway, then enter the TCP/IP address of this gateway on the upper network, in example : 10.10.4.2
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 123 / 173
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.
3 – From the IEC61850 protocol, launch the "Edit relation" in the contextual menu, click on the tab "To", click on the item "transmits: Datapoint [0..655535]".
The list of datapoints, which can be linked to this protocol is displayed, select the electrical and system datapoints you want to be transmitted to the upper network and click on Apply Please note that the selected datapoints must have an IEC address. 4 - "Check in" (1.0 release) and "Generate" the lower database. Before starting the next steps, please ensure that the files: "Energy_lower.1.0.bup.zip", "Energy_lower.1.0.zip" and "Energy_lower.1.0.scadaSbusDm.zip" under the directory target of the generation. 5 - Extract the "GTW_IEC_PROT0.xml" file from "Energy_lower.1.0.scadaSbusDm.zip" archive.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 124 / 173
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 - Copy the lower database file (Energy_lower.mpc) in order to use it as base of work for the upper database file (Energy_upper.mpc).
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 125 / 173
15.2 "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 authorization.
The actions described below are the first actions the user have to process. 1 - Open the upper database (Energy_upper.mpc) and delete all IEC physical device from system part (Scs), all interlock and FBD equations. Don’t' change the name of the substation. 2 - 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 gateway on the lower network, in example: GTW_IEC and TCP/IP address: 10.10.4.2
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 126 / 173
3 – From the gateway, launch the "Edit relation" in the contextual menu, click on the tab "To", click on the item "manages: Bay [0..655535]".
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 list of bays, which can be managed by the gateway is displayed. Select those you want to be managed by the gateway, then click on Apply. Datapoints you wish to use on the upper network need to be part of the selected bays.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 127 / 173
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 - At this stage, you can import the xml model "GTW_IEC_PROTO0.xml" file.
For this import, do the following actions:
-
From "Tools" menu, select "Manage IEC61850 IED" options,
- Click on "Import …" to browse the PC in order to find out the xml file, AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 128 / 173
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 Upper bow, select the xml file, in the bottom listbox , select the GTW, the Click on "Set" button (a message box is displayed "IED model import in progress, please wait")
-
Click on "Close" (a message box is displayed "IED model setting in progress, please wait")
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. 5 - Change the "short name", "long name", "network name" and "TCP/IP address" of OI server to be compatible with upper network. 6 - Fill the relation between OI server and IEC/IEC gateway (named "has for UCA2/IEC server"). 7 - Check in and generate the upper database before completing the rest of the configuration.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 129 / 173
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.
16. ARCHIVE TRENDVIEWER PACIS OI CLIENT
ON
STANDALONE
This chapter describes how to configure an Archive Trendviewer on a remote PACiS OI Client. Following the displaying of a mimic including an Archive Trendviewer, display the menu to allow to add pen (Quick Settings):
Click on Add Pen. The “Trend DataSource Selector” view is displayed with Browse button unavailable:
Click on Add DS.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 130 / 173
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 “ Database Setup ” view is displayed with all buttons unavailable:
Write something on Display Name: buttons are available:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 131 / 173
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 S2KTrend, verify the Server name is the good one: the name of PACiS OI server. If it’s not, write it, in example: PACP0005.
Click on Apply, then click on Test to verify the good connection of the Database. Select the last Database (the new one, created above) and click on Remove. Click on Finish. Now the Browse button of the “Trend DataSource Selector” View is available. You can browse the Database to select a variable.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 132 / 173
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. WINDOWS XP This chapter describes the process to use and install PACiS components on Windows XP Operating System. The Windows XP OS must be set-up as "Administrator". After power-on the PC, go to the session of Administrator
If there is no "Administrator" username displayed, click twice on "Ctrl+Alt+Suppr", then enter the username "Administrator" and the corrected Password.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 133 / 173
17.1 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 authorization.
Modification of temp path: Edit the "SCE_settings.xml" "SCETmpPath":
(with
Notepad),
change
the
,
value
of
item
Type="Path"
By the temporary directory C:\Temp, you have to create it, if this directory is not existed.
Type="Path"
To be able to use correctly IsaGraf tool, you have to use also the dongle management software : Sentinel Protection. This software is available at : Driver dongle
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 134 / 173
17.2 OI/SMT & 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 authorization.
17.2.1 Deactivation of Security Center Start>Settings>Control Panel
Click on "Performance and Maintenance"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 135 / 173
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 "Administrators Tools"
Click on "Component Services"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 136 / 173
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 "Security Center" from "Services (Local)" item. Click right on Properties menu:
Select "Disabled" for the "Startup Type", then click on OK.
17.2.2 Deactivation of Firewall From "Components Services", select "Windows Firewall/Internet Connection:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 137 / 173
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 right on "Properties" menu:
Select "Disabled" for the "Startup Type", then click on OK.
17.2.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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 138 / 173
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".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 139 / 173
17.2.4 Settings for DCOM
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.
1. Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to configure permissions:
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"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 140 / 173
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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 141 / 173
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. For all Groups and user names, allow "Local Access" and "Remote Access", then click on OK 9. Do the same on "Edit Default"
10. Click on "Edit Limits in "Launch and Activation Permissions" item
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 142 / 173
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.
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"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 143 / 173
17.2.5 Folders options
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.
Launch "Explorer" software, Tools item, Folders options, View Tab, deselect the last line "Use simple file sharing (Recommended), then click on OK:
17.2.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:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 144 / 173
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.
1. C:\SharedWorspace:
Select "Permissions" and for "Everyone", Allow "Full control", "Change" and "Read". 2. C:\Temp\trace:
Select "Permissions" and for "Everyone", Allow "Full control", "Change" and "Read".
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 145 / 173
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.
3. C:\Program files\AREVA\PACiS\PACiSOI\Server\MemoFolder:
17.2.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
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 146 / 173
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.2.8 PACiS GTW –PC: Protocol OPC: Setting for DCOM 1.
Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to configure permissions on "OPC DATA IMPLEMENTATION" component.
2.
Select "OPC DATA IMPLEMENTATION", click right and select Properties
3.
Select Security Tab, set "Use Default" for "Launch and Activation Permissions" and for "Access Permissions", set "Customize" for "Configuration Permissions"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 147 / 173
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.
Click on "Edit…" for "Configuration Permissions"
5. For all Group and user names, allow "Full Control" and "Read", then click on OK 6. Select Identity Tab
7. Select "The interactive user", then Click on OK
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 148 / 173
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.2.9 PACiS OI: Setting for DCOM 1.
Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to configure permissions on "S2K.OpcServer" component.
2.
Select "S2K.OpcServer", click right and select Properties
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"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 149 / 173
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 for "SCADA 2000 C2KAlarmServer"
7.
Do the same configuration for "SCADA 2000 Server.exe"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 150 / 173
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 for "USDATA Trend Datasource Server"
10. Go to "Identity" Tab, select "The interactive user"
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 151 / 173
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.
18. TREND VIEWER REAL TIME
18.1 Overview The Trend Display is a special animation that produces a display of up to 8 Register (Measurement MV) or Bit variables (SPS, DPS) plotted against time. You can embed any number of Trend Displays in a mimic, with the only limitation the amount of physical space available. The limit to the number of Trend Displays that you can configure should be evaluated at the validation time.
A typical Trend Display looks similar to the following.
Each Trend Display contains a configurable display buffer where a temporary historic record of the values for each trace is stored. The values in the buffer can be displayed on the chart using the scrollbar.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 152 / 173
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.
When a mimic containing a Trend Display initially is opened, the buffer is empty. As the buffer fills, the size of the slider on the scrollbar changes to reflect the amount of data stored as a ratio of the chart period. For example, if the buffer contains ten minutes of data and the chart is two minutes in duration, the slider is approximately one-fifth the length of the scrollbar.
18.2 Run-time mode Display In run-time mode, the Trend Display plots the value of a maximum 8 database variables (bit or register) against time. The horizontal axis represents time; the vertical axis represents value. Each Trend Display contains a configurable display buffer where values of the database variables for each trace are stored. In a real-time Trend Display, the display buffer temporarily records values for the traces, providing a limited ability to scroll back in time. The Trend Display operates in two modes during runtime. Each of these modes is described in a separate topic: •
Real Time Mode: traces are plotted on the chart in real time as the values of the variables they represent change. You can configure a Trend Display so that it starts in real time or can be selected with the play arrow on the toolbar at runtime.
•
Pause Mode: traces are plotted on the chart from the values of variables recorded in the display buffer. You can switch the Trend Display from real time to pause mode by selecting the pause arrow from the toolbar or by using the scrollbar.
18.2.1 Trend Real-Time mode
In real-time mode, new values for each trace are plotted starting on the right side of the chart. Older data scrolls across the chart, eventually disappearing off the left side. The frequency at which the chart is refreshed depends on the configuration and how often the data changes. •
The chart is always updated when any variable changes value.
•
The chart is also refreshed at a background rate determined by the configuration of the Trend Display. For example, if the background refresh is set to 5, the chart refreshes every 5 seconds even if none of the variables has changed. The value of this parameter is set to 2 by default.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 153 / 173
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.
A Trend Display records temporary historic data in its display buffer. The buffer continues to record data continually while the trend is displayed, discarding the oldest values when it becomes full. As the buffer fills, the size of the slider on the scrollbar changes to reflect the amount of data stored as a ratio of the chart period.
18.2.2 Trend Pause mode
The Trend Display automatically switches to pause mode when you click and drag the slider button on the scrollbar or when you select the pause tool. In pause mode, the chart area no longer updates in real-time; instead, it displays the temporary historic data recorded in the display buffer. However, the buffer of the Trend Display is still updated in real-time, with the oldest values being discarded. The effect of this is that the data being displayed on the chart is gradually moving through the buffer. To represent this visually, the slider button on the scrollbar moves gradually toward the left. If you leave the Trend Display in pause mode long enough, the data for the time period displayed is discarded. When the Trend Display is in pause mode, you can scroll backward and forward through the data using the scrollbar. You can also zoom in and zoom out in both the X and Y axes using either the toolbar or the cursor 18.2.3 Using the Toolbar
The toolbar (left part of the trend mimic) contains the tools used to select the mode and for simple zooming in and out of the chart time axis.
Select Real-Time mode. Select Pause mode. Explode the time axis. The time axis is doubled. Implode the time axis. The time axis is halved. Restore the time axis to its original setting. Print the Trend Display on the default printer. Select Cursor mode. Zoom in area. AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 154 / 173
Zoom in time axis only.
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.
Return to previous zoom level. Cancel all zooming. Select the default cursor. Selecting this button disables the Cross Cursor. Restore the trend to its original configuration. Change the period for the time axis in units of seconds, minutes, hours, or days. Select cross cursor mode. Selecting this button disables the Default Cursor.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 155 / 173
18.2.4 Using the Cursor
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.
When in pause or historic mode, you can use the cursor to interact with the chart area. Using the cursor you can do the following: •
Display the value of each of the traces at a particular point in time.
•
Zoom the trend in the time (horizontal) axis.
•
Zoom the trend simultaneously in both the time (horizontal) axis and value (vertical axis).
Select the operating mode for the cursor from either the toolbar or a pop-up menu displayed by right-clicking anywhere in the chart area.
Cross cursor illustration:
Click anywhere in chart area and a cross cursor appears. In this figure the value appears at the left side (350) and the time stamp on the bottom side (06/09/2006 13:53:43). AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 156 / 173
18.2.4.1 Displaying the Value of Traces
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.
1. Select the cursor tool. The mouse pointer displays as a cross while it is over the chart area. 2. Click anywhere in the chart. The values for the traces at that point are displayed in the Legend area or in the Scale area, if visible. 18.2.4.2 Zooming the Time Axis
1. Select the zoom time axis tool. The mouse pointer changes to a magnifying glass while it is over the chart area. 2. Click on the chart at the point that represents the new start time for the chart. 3. Hold down the mouse button and drag the cursor to the point that represents the new end time. 4. Release the mouse button. 18.2.4.3 Zooming Both Axes
1. Select the zoom area tool. The mouse pointer changes to a magnifying glass while it over the chart area. 2. Click on the chart at the point that represents the new start time and maximum value for the chart. 3. Hold down the mouse button and drag the cursor to the point that represents the new end time and minimum value. 4. Release the mouse button.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 157 / 173
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.
18.2.5 Using the Scrollbar
Use the scrollbar to select data in the display buffer for display on the chart. You can get an approximate idea of the ratio of the number of values that might display in the chart to those held in the buffer by the size of the scroll button in relation to the area in which it may be moved. The way in which the scrollbar tools behave varies slightly depending on which mode the Trend Display is in, as described in the following table:
Real-Time Mode
Pause Mode
Select Pause mode and scroll to the oldest data in the display buffer.
Scroll to the oldest data in the display buffer.
Select Pause mode and scroll back through data in the display buffer.
Scroll back through data in the display buffer.
No action.
Scroll forward through the data in the display.
No action.
Select Real-Time mode.
Display the Trace Toolbox.
Display the Trace Toolbox.
Select Pause mode and scroll through the data in the display buffer.
Scroll through the data in the display buffer.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 158 / 173
18.2.6 Using the Toolbox
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.
Use the Curves tab to specify the appearance of each trace in your Trend Display.
Set the following to configure Curves for the Trend Display: o
Visibility – Enables individual traces to be hidden temporarily. This can be useful when one trace obscures another
o
Color – allows to change the color of each trace
o
Name – Name for each trace
o
Min/Max – allows to change the range for each trace
o
Real – Displays values received
o
Cursor – Display values where the cursor is
o
Advanced Properties – allows access to the toolbox advanced properties, all of which may be individually enabled / disabled. Select from the following:
Select Variable – allows to change the variable for each trace. (See remark below)
Trace Width – allows to change the width of each trace
Trace Style – allows to change the plotting style for each trace:
Each point representing a change in value is connected to the previous one with a single line.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 159 / 173
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.
Each point representing a change in value is connected to the previous one with a vertical and horizontal line.
Each point representing a change in value is plotted with no interconnecting lines. Remark:
The access to change variable for each trace is done by a “Variable Browser” window. It allows, via an OPC browser, to reach the variable to trace.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 160 / 173
19.1 Scope This paragraph details for the SCE the way to use the PIX template in order to manage motor driven switch gear equipment according to the control requirements implemented in the P139 IED protection. The PIX template is intended to cover the control command functions needed for the management of PIX cubicles. The template covers the needs described in the PIX Control Specification Issue A document approved by the customer. This paragraph will develop the composition of the template and then how to use the template delivered in 'PIX_Template'directory.
19.2 Template Composition 19.2.1 Automatisms There are 7 automatisms in the template and they are all linked together by one or several data points. These automatisms are listed in the table below: Name of the automatism in the specification
MOTOR-DRIVEN DEVICES DIRECT CONTROL MANAGEMENT
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.
19. PIX CUBICLE TEMPLATE
Name of the automatism
Origin
Function
Actions from specification treated
Request Manageme
Slow automation (ISAGRAF)
Manages the user request and the return of the request if needed
A0-0; A0-1
MRStat Control
FBD Automation
Manages the MRStat signal and the SWD_T timer
A1-2; A1-4; A2-3; A2-4
Output Man
FBD Automation
Manages the outputs of the PIX function
A3-4; A4-0
Termination Man
FBD Automation
Manages the termination signals received from organs commanded
A1-4; A2-3
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 161 / 173
OVERHEATING MOTOR PROTECTION
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.
Close Interlock
FBD Automation
Manages the interlock equation of the close request
A0-0; A0-1
Open Interlock
FBD Automation
Manages the interlock equation of the open request
A0-0; A0-1
Overheating Prot
FBD Automation
Manages the overheating protection of the motor
All actions of OverHeating protection automatism
19.2.2 Detailed description of the different automatisms 19.2.2.1 "Request Manageme" automatism This automatism manages the request of the user. Inputs: Name
Type
Purpose
Origin
Open/Close PIX
DPC
Operator input for open or close. From local HMI, OI, Gateway
Operator
CtrlClSPS
SPS
External electrical wired input for close control of the device
Wired
CtrlOpSPS
SPS
External electrical wired input for open control of the device
Wired
DPS
DPS
Device status signal open and close.
Controlled by two wired SPS (Device Close and Device Open)
Fail
SPS
Fail of the termination signal reception
Termination Man FBD
FeedBack SPS MRD
SPS
Feedback to stop running commands
Output Man FBD
ILK Close
SPS
Interlock for close command. 0: enable the command, 1: disable the command
Interloclk Close FBD
ILK Open
SPS
Interlock for open command. 0: enable the command, 1: disable the command
Interlock Open FBD
MD_INHIB
SPS
Inhibition of the commands. 0: enable the command, 1: disable the command
OverHeating Prot FBD
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 162 / 173
Outputs:
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
Type
Purpose
OReq
SPS
Open request sent to the other automatisms
CReq
SPS
Close request sent to the other automatisms
This automatism acquires the operator command and checks for the interlocks and inhibition conditions. The operator command could be issued from local HMI, OI, Gateway or from an external input. When the operator request is Open/Close PIX, the automatism sends an acknowledgement to the command in order to end correctly the sequence. When the operator acknowledgement.
request
is
CtrlClSPS
or
CtrlOpSPS,
there
is
no
The automatism manages itself the validity of the request of the operator regarding the position of the device. For example, if it is closed and the operator sends a close request, the control of the breaker is not issued and a negative acknowledgement is sent to the command if the DPC was used.
19.2.2.2 "MRStat Control" automatism This automatism manages the MRStat signal and the SWD_T timer. It controls the presence of the MRStat signal within the configured time of MRS_Mon_T delay. It controls also the presence of a termination signal before the SWD_T timer elapses. Inputs: Name
Type
Purpose
Origin
And Latch
SPS
Stop the SWD_T timer if a termination is received
Output Man FBD
MRDSPC
SPS
Starts the MRS_Mon_T timer
MRDSPC data point
MRStat
SPS
Stop the MRS_Mon_T timer
Wired
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 163 / 173
Outputs:
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
Type
Purpose
FailSWD
SPS
Indicates that the action takes too much time and that the motor must stop
MR_StartRTMon
SPS
Indicates that the motor started correctly in time and is used by the overheating protection to count the number of operations of the motor
MRStart Raised
SPS
Indicates that the motor started in time
NoMRStat
SPS
Indicates that the motor did not start in time
Automatism:
19.2.2.3 "Output Man" automatism This automatism manages the outputs of the PIX automatism, i.e.: last automatism before the outputs contacts. It controls if the operation ended correctly and manages the Latch_T timer. Inputs: Name
Type
Purpose
Origin
Close Cmd
SPS
This SPS is used to set : SWDSPC DO, MRDSPC DO and Close to their value
Request Manageme automatism
slow
Close Cmd bis
SPS
This SPS is the same as Close Cmd but is used to set the feedbacks of the xPC and to reset the RS rocks.
Request Manageme automatism
slow
Fail SWD
SPS
Stops everything and sets the Fail output to indicate there was a failure in the action
Controle MRStat FBD
Fail Termination
SPS
Stops everything and sets the Fail output to indicate there was a failure in the action
Termination Man FBD
MRStat Raised
SPS
One of the condition to indicate that everything got well
Controle MRStat FBD
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 164 / 173
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.
NoMRStat
SPS
Stops everything and sets the Fail output to indicate there was a failure in the action
Controle MRStat FBD
OK Termination
SPS
One of the condition to indicate that everything got well
Termination Man FBD
Open Cmd
SPS
Same as Close Cmd but for the open request
Request Manageme automatism
slow
Open Cmd bis
SPS
Same as Close Cmd bis but for the open request
Request Manageme automatism
slow
Outputs are: Name
Type
Purpose
And Latch
SPS
Indicates that all the conditions are present to tell that the action did well
Close
SPS
Controls the Close state of DDPC
Fail
SPS
Indicates that the action did not end well
FeedBacksSPS Clos
SPS
Is used as feedback of DDPC data point to reset it
FeedBackSPS MRD
SPS
Is used as feedback of MRDSPC data point to reset it
FeedBackSPS Open
SPS
Is used as feedback of DDPC data point to reset it
FeedBackSPS SWD
SPS
Is used as feedback of SWDSPC data point to reset it
MRDSPC DO
SPS
Controls the state of the MRDSPC data point
Open
SPS
Controls the open state of DDPC
SWDSPC DO
SPS
Controls the state of the SWDSPC data point
Automatism:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 165 / 173
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.
19.2.2.4 "Termination Man" automatism This automatism controls the open or close termination input signals. It generates two SPS: one for normal termination (OK) and one for abnormal termination (Fail) according to the signal received and the state of the motor. See Automatism scheme. For example, if the signal received is an open termination whereas the request was a close, nothing is done. Inputs: Name
Type
Purpose
Origin
CloseTerm
SPS
Indicates that a close term signal is received
Wired
CReq
SPS
Check if the termination received corresponds to this request
Request Manageme slow automatism
Device_Close
SPS
Indicates that a close signal is received
Wired
Device_Open
SPS
Indicates that an open signal is received
Wired
MRStat
SPS
Check that a termination signal is not received before the motor started
Controle MRStat FBD
MRStat Raised
SPS
Check if can send OK signal
Controle MRStat FBD
NoMRStat
SPS
Check that a termination signal is not received before the motor started and if the MRS_Mon_T timer elapsed
Controle MRStat FBD
OpenTerm
SPS
Indicates that an open term signal is received
Wired
OReq
SPS
Check if the termination received corresponds to this request
Request Manageme slow automatism
Outputs: Name
Type
Purpose
Fail
SPS
Indicates that a termination signal is received during the MRS_Mont_T timer and before the motor started
Ok
SPS
Indicates that a termination is received and it corresponds to the request of the user
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 166 / 173
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.
Automatism:
19.2.2.5 Interlock Close and Open automatisms Those automatisms are accessible to the SCE configurator to set the interlock equations up. The only limitations is not to modify the Open or Close output respectively ILK Open, ILK Close. Outputs: Name
Type
Purpose
ILK Close
SPS
This output is the one of Interlock Close FBD and indicates that there is an interlocking with the close request. 1: disable command, 0: enable command
ILK Open
SPS
This output is the one of Interlock Open FBD and indicates that there is an interlocking with the open request. 1: disable command, 0: enable command
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 167 / 173
19.2.2.6 "OverHeating Prot" automatisms
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.
This automatism is counting the number of motor operation. It disables motor control if the number of operation is over the parameter “MR_PermOp” for a given time “MR_CoolT”. Note: See how to modify MR_PermOp in the chapter "". Inputs: Name
Type
Purpose
Origin
Inhibit
SPS
Reflect of the signal MD_INHIB sent by itself
OverHeating Prot FBD
MR_StartRTMon
SPS
Can be considered as a clock signal and is used to increase the counter
Controle MRStat FBD
RstMon
SPC
Resets the counter and the MR_CoolT timer
Operator
Outputs: Name
Type
Purpose
INHIBIT
SPS
Indicates that the motors started and stopped too many times in less than MR_CoolT timer and blocks the user actions. 1: disable command, 0: enable command
OPCpt_x
SPS
These outputs indicate at which step the counter is.
Automatism:
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 168 / 173
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660
Page: 169 / 173
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.
19.2.3 Description of the data points in relation with the specifications
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.
19.2.3.1 Inputs Specification Name
Template Type
Name
Type
DPS
DPS
DPS
DPS controlled by 2 SPS: Device Close and Device Open
MRstat
SPS
MRStat
SPS
OpenTerm
SPS
OpenTerm
SPS
CloseTerm
SPS
CloseTerm
SPS
SWTPSPS
SPS
NA
CtrlOpSPS
SPS
CtrlOpSPS
SPS
CtrlClSPS
SPS
CtrlClSPS
SPS
19.2.3.2 Outputs Specification Name
Template Type
Name
Type
DDPC
Double pole DPC
DDPC
Double pole DPC
MRDSPC
Double pole SPC
MRDSPC
Double pole SPC
SWDSPC
Double pole SPC
SWDSPC
Double pole SPC
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 170 / 173
19.3 How to use the PIX Template
-
A bay including the automatisms and the data points necessary to control the PIX
-
The profiles of the different Data Points
19.3.1 Use of the PIX Template at the SCE level There are 8 steps to respect in order to use the template properly. 1. Create an instance of the template in the Electrical part 2. Move the profiles created under Temporary system to the “system profiles” 3. Break the link with the template 4. Edit the link “is managed by : ” to associate the bay with a C264 5. For each automatism: edit the link “runs on : PLC”. Select the PLC of the C264 which manages the bay 6. For wired data points listed in the table below, complete the link “wired on : ” or “wired on : ”
Wired on :
Link type
Wired on :
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 PIX template includes:
Name
Purpose
CloseTerm
status signal for external Close command termination
CtrlClSPS
External electrical input for close control of device
CtrlOpSPS
External electrical input for open control of device
Device Close
Device status signal for close
Device Open
Device status signal for open
MRStat
Status signal of motor relay
OpenTerm
Status signal for external Open command termination
DDPC
Device Open/Close DO. This one is particular because it has two relations of wiring, one for the Open order and one for the Close order.
MRDSPC
Motor relay double pole contact single point control DO
SWDSPC
Shunt winding double contact single point DO
7. Do a “SBUS Automatic Addressing…” on the C264 which contains the bay AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 171 / 173
8. As per all other command in the SCE, the operator request open or close could be part of a graphical view.
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.
19.3.2 Configure the parameters of the PlX The parameters are set to default value in the template. To configure the PIX, there are 5 parameters which are the duration of the timers. The parameters are: Name
Purpose
SWD_TP
operating time Parameter
Latch_TP
of
switching
[min, def, max] device
timer
Unit
Step
[100, 20, 254]
S
100ms
Latching time timer Parameter
[0, 0, 5]
S
10ms
MR_MON_TP
time of motor relay timer Parameter
[10, 100, 2000]
Ms
10ms
MR_CoolT
Motor Relay Cooling Timer
[0, 3, 10]
Min
NA
MR_PermOp
Motor Relay Permissible Operation
[1, 15, 20]
1
19.3.2.1 Configure the SWD_T timer To configure this timer, you have to change the value of the SWD_TP parameter. To do this:
-
open the MRStat Control FBD
-
search for the TON with associated text SWD_T
-
change the value of the TON within the limits defined in the Parameters table
See MRStat Control Automatism scheme to localize the timer.
19.3.2.2 Configure the Latch_T timer To configure this timer, you have to change the value of the Latch_TP parameter. To do this:
-
open the Output Man FBD
-
search for the TON with associated text Latch_T
-
change the value of the TON within the limits defined in the Parameters table
See Output Man Automatism scheme to localize the timer. AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 172 / 173
19.3.2.3 Configure the MRS_Mon_T timer and MR_Mon_T timer CAUTION: The timers “MRS_Mon_T” and “MR_Mon_T” must have the same 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 authorization.
To configure these timers, you have to change the value of the MR_MON_TP parameter by proceeding as described below:
-
open the MRStat Control FBD
-
search for the TON with associated text MRS_Mon_T
-
change the value of the TON within the limits defined in the Parameters table
-
on the electrical view in the SCE, search for the data points SWDSPC and DDPC and do the following changes :
o in the attribute list, search for the attribute “hold duration (ms)” in the Delays part of the General attributes o change the value of this attribute according to the value you set in the MRStat Control FBD See MRStat Control automatism scheme to localize the timer.
19.3.2.4 Configure the MR_CoolT timer To configure this timer, you have to change the value of the MR_CoolT parameter. To do this:
-
open the OverHeating Prot FBD
-
search for the TON with associated text MR_CoolT
-
change the value of the TON within the limits defined in the Parameters table
See OverHeating Prot automatism scheme to localize the timer.
19.3.2.5 Configure the MR_PermOp parameter To configure this parameter, you must open the FBD editor and move the INHIBIT output to the position corresponding to the number of permissible operation you want to set. See OverHeating Prot automatism scheme to localize the INHIB output to move.
AREVA PACIS V4.4 ReadMe RM – Issue C – 30/07/07
Identification Number: 2059660 Page: 173 / 173
View more...
Comments
