PACiS V4.4 ReadMe_J
Short Description
pa...
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 PACiS V4.4
DISTRIBUTION Confidentiality Category Restricted
Control Category
Normal
Controlled
Not Controlled
Identification number
Identification letters
Issue
Transmission & Distribution
2059660
RM
J
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 J – 07/07/08
Identification Number: 2059660
Page: 2 / 128
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 J – 07/07/08
DATE
SIGNATURE
Identification Number: 2059660 Page: 3 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 4 / 128
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
30/07/07
G. JUVANON
Delivery of C264 VB4.54B, EQ_SIM V1.6.4, GTW V4.22.7, OI G.03.06A with SCADA 2000 M4RC62A, SCE V4.46, SBUS Agency V4.4 and SMT K.00.04 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)
D
31/08/07
G. JUVANON
Delivery of C264 VB4.57F, GTW V4.22.11, OI G.03.06C with SCADA 2000 M4RC62C, SCE V4.47 Adding information on Configuration databag download into the C264 from the CMT tool Adding information on configuration alarm LED and on new acq type for MODBUS legacy protocol
E
05/10/07
G. JUVANON
Delivery of C264 VB4.60B, GTW V4.23.1, OI G.03.07C with SCADA 2000 M4RC63C, SCE V4.48, SBUS Agency V4.6B, SMT K.00.05 Adding information on DP Unknown management configuration Adding information on Russian Report Templates and on OI Report configuration
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 5 / 128
F
07/12/07
G. JUVANON
Delivery of C264 VB4.62, GTW V4.24, OI G.03.07G with SCADA 2000 M4RC63G, SBUS Agency V4.7C, SCE V4.48.B
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 information on login and password for CMT/Telnet Adding information on OI Buffer report configuration Adding information on Energy values transmitted as counter for DNP3 & CDC II protocol on GTW-PC (CRA 1031) Modification on SBUS Agency installation Modification on DCOM Settings on Windows 2000 Adding information on updating time of a HOPF 6039 board into GTW-PC for DNP3, T101 and CDCII protocols G
28/01/08
G. JUVANON
Delivery of OI C264 VB4.63, OI G.03.06I with SCADA 2000 M4RC63I, SBUS Agency V4.8, SCE V4.48.D Adding information on Bay Alarm Acknowledgement configuration Adding information on Synchro SNTP with third party device Adding information for configuring Windows Time service for PC as SNTP server and as SNTP Client
H
10/03/08
G. JUVANON
Delivery of OI C264 VB4.66, GTW V4.24.5, OI G.03.07J2 with SCADA 2000 M4RC63J2, SBUS Agency V4.8B, SCE V4.48.H, SMT K.00.07 Adding information Time configuration Adding information to deactivate the "Error Reporting" for Dr Watson on Windows 2000
I
22/05/08
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
G. JUVANON
Delivery of OI C264 VB4.68A, GTW V4.24.6, OI G.03.07L with SCADA 2000 M4RC63L, SBUS Agency V4.10, SCE V4.48.J, SMT K.00.08
Identification Number: 2059660 Page: 6 / 128
J
07/07/08
G. JUVANON
Delivery of OI C264 VB4.70, GTW V4.25.1, OI G.03.07M with SCADA 2000 M4RC63M, SBUS Agency V4.11, SCE V4.48.K, SMT K.00.09 Deactivation of the copy of persistence file from Master to Backup OI 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.
Adding information on SocketLimitationExtension software (extend the number of TCP connection attempts on PACiS OI)
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 7 / 128
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 ...................................................................................................................................................10
2.
OPERATOR INTERFACE........................................................................................................................11
2.1 OI INSTALLATION ......................................................................................................................................11 2.1.1 Standard installation ............................................................................................................................11 2.1.2 Stand-alone OI client installation.........................................................................................................13 2.2 WINDOWS TIME SERVICE - SNTP ..............................................................................................................17 2.2.1 Windows XP..........................................................................................................................................17 2.2.2 Windows 2000 ......................................................................................................................................18 2.3 SQL SERVER 2000.....................................................................................................................................19 2.3.1 SQL Server Agent Service.....................................................................................................................19 2.4 SQL SERVER 2005.....................................................................................................................................20 2.4.1 SQL Server Agent Service.....................................................................................................................20 2.4.2 Russian Report Templates ....................................................................................................................22 2.5 WINDOWS 2000 .........................................................................................................................................23 2.5.1 Settings for DCOM ...............................................................................................................................23 2.5.2 Deactivation of "Error Reporting" .......................................................................................................30 3.
PACIS WATCH ..........................................................................................................................................32
4.
SYSTEM MANAGEMENT TOOL ...........................................................................................................35
5.
SYSTEM CONFIGURATION EDITOR ..................................................................................................37
6.
COMPUTER C264......................................................................................................................................39
6.1 COMPUTER INSTALLATION.........................................................................................................................39 6.2 RUSSIAN / CHINESE LANGUAGE CONFIGURATION ......................................................................................40 6.3 C264 BOOT PARAMETERS RESTORATION ....................................................................................................41 6.4 C264 CONNECTION ....................................................................................................................................44 6.4.1 Connection CPU260.............................................................................................................................44 6.5 CONFIGURATION DOWNLOAD LOAD INTO THE C264..................................................................................45 6.6 TELNET FROM CMT...................................................................................................................................45 7. 7.1 8. 8.1 8.2 9.
GATEWAY..................................................................................................................................................46 HOPF 6039 BOARD .....................................................................................................................................47 STATION BUS AGENCY ..........................................................................................................................48 INSTALLATION ...........................................................................................................................................48 USE SBUS AGENCY FILE AS DLL ...............................................................................................................52 TUNNELLING MODE...............................................................................................................................55
9.1 TUNNELLING MODE THROUGH SERIAL PORT ..............................................................................................55 9.2 TUNNELLING MODE THROUGH ETHERNET NETWORK .................................................................................56 9.2.1 Installation of tunnelling components...................................................................................................57 9.2.2 Launch the tunnelling ...........................................................................................................................58 10.
CONFIGURATION INFORMATION .................................................................................................59
10.1
SCE CONFIGURATION................................................................................................................................59
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 8 / 128
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.1 OI PRINTER CONFIGURATION ....................................................................................................................73 10.1.1 OI Printer : Marked characters .......................................................................................................73 10.1.2 Printing spooler configuration.........................................................................................................73 10.2 COMPUTER PRINTER CONFIGURATION.......................................................................................................74 10.3 TIME CONFIGURATION ...............................................................................................................................75 10.4 INTEGRATION OF A NEW RELEASE OF TZTAB FILE ......................................................................................76 11.
ISAGRAF AUTOMATION ...................................................................................................................77
11.1 11.2
SCE: MULTI DO IN THE SAME STEP ...........................................................................................................77 USE OF MPS DATAPOINTS .........................................................................................................................79
12.
OI PRINTER STATES...........................................................................................................................80
13.
OI TWIN SERVER SAFE FUNCTION ...............................................................................................81
13.1 SPECIFICATION ..........................................................................................................................................81 13.2 CONFIGURATION AND SETTINGS ................................................................................................................82 13.2.1 SCE Configuration ...........................................................................................................................82 13.2.2 Setting Twin Server Safe ..................................................................................................................82 13.2.3 Modify files for Twin servers safe function ......................................................................................83 13.2.4 PACiS OI Client – connection to servers .........................................................................................86 13.3 FAILURE CASES ..........................................................................................................................................87 13.3.1 Loss of Master PC ............................................................................................................................87 13.3.2 Loss of Remote PC ...........................................................................................................................87 13.3.3 Backup Historian Data Base............................................................................................................88 13.3.4 Restore Historian Data Base............................................................................................................88 13.3.5 Copy Historian backup file ..............................................................................................................88 13.3.6 Copy Persistence files ......................................................................................................................89 14.
IEC61850 / IEC61850 GATEWAY .......................................................................................................90
14.1 14.2
"LOWER" NETWORK...................................................................................................................................91 "UPPER" NETWORK ....................................................................................................................................93
15.
ARCHIVE TRENDVIEWER ON STANDALONE PACIS OI CLIENT ..........................................98
16.
WINDOWS XP .....................................................................................................................................101
16.1 SCE .........................................................................................................................................................102 16.2 OI/SMT & GATEWAY ..........................................................................................................................103 16.2.1 Deactivation of Security Center .....................................................................................................103 16.2.2 Deactivation of Firewall ................................................................................................................105 16.2.3 Deactivation of "Error reporting"..................................................................................................106 16.2.4 Settings for DCOM.........................................................................................................................108 16.2.5 Folders options...............................................................................................................................112 16.2.6 PACiS OI: Shared Folders .............................................................................................................112 16.2.7 PACiS OI/SMT: Network configuration.........................................................................................114 16.2.8 PACiS GTW –PC: Protocol OPC: Setting for DCOM..................................................................115 16.2.9 PACiS OI: Setting for DCOM .......................................................................................................117 16.2.10 PACiS OI: Socket Limitation Extension software .........................................................................120 17.
CONFIGURABLE REPORTS CREATION......................................................................................123
17.1 17.2
HOW TO USE THE CONFIGURE A REPORT FROM THE SCE .........................................................................123 HOW TO USE A REPORT CREATED BEFORE PACIS V4.4.4 ........................................................................124
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 9 / 128
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 PC of the application. Operating System: • •
Windows 2000 SP4 Windows XP SP2
If you install SCE, OI or Gateway on Windows XP Operating System, the §16 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. Do not use anymore the former IED Mapper delivered outside the SCE. Use mandatory the IED mapper delivered with the SCE. OI Server redundant : Twin Server Safe The copy of persistence files from Master to Backup OI Server has been disable. So, there is no need to modify the registry key of the Twin Server Safe function. Therefore, after a switch of OI Client connected to the OI Server Backup, the user has to acknowledge the alarms.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 10 / 128
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.07M" 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_M4RC63M folder which contains the SCADA 2000 application (S2K M4 RC63M)
•
the SNTP folder which contains files to configure a SNTP client or a SNTP server (see § 2.2)
•
the SocketLimitationExtension folder which contains software to extend the limitation of 10 concurrent TCP connection attempts (see § 16.2.10)
•
the Twin Server Safe Settings folder which contains files to define the setting for the Twin Server Safe function (refer to § 13)
2.1 OI installation 2.1.1 Standard installation For PACiS OI Server, it is mandatory to setup a complete installation of PACiS OI (server & client) and SCADA 2000. 1. Check if SQL Server 2000 is installed (see information § 2.3) or if SQL Server 2005 is installed (see information § 2.4) – 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"), AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 11 / 128
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. Launch S2K M4RC63M\M4RC63M_setup.exe to install SCADA 2000 application (custom installation, don't change the default path of the installation (C:\Program Files\USDATA)
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 J – 07/07/08
Identification Number: 2059660 Page: 12 / 128
2.1.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 J – 07/07/08
Identification Number: 2059660 Page: 13 / 128
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
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 14 / 128
4. 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 J – 07/07/08
Identification Number: 2059660 Page: 15 / 128
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. 5. 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 J – 07/07/08
Identification Number: 2059660 Page: 16 / 128
2.2 Windows Time service - SNTP
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.2.1 Windows XP Directory : SNTP/WXP SNTP Server: •
launch the "SNTP_Server\w32time_parameters.reg to update the Windows registry
•
launch "SNTP_Server\w32time.cmd" file to restart the Windows Time service
•
put the w32time.cmd file in the startup folder of the PC
SNTP Client: •
open the "SNTP_Client\w32time_parameters_one_server.reg" file if only one server is master clock or "SNTP_Client\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 device defined as SNTP server in the configuration)
•
launch the "SNTP_Server\w32time_parameters_one_server.reg" or "SNTP_Server\w32time_parameters_two_servers.reg" to update the Windows registry
•
Normally, these parameters must be updated by SBUS Agency
•
Don't use synchronisation on Date and Hour Properties
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 17 / 128
2.2.2 Windows 2000 Directory : SNTP/W2K
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.
SNTP Server: •
launch "SNTP_Server\w32time.cmd" file to restart the Windows Time service
•
put the w32time.cmd file in the startup folder of the PC
SNTP Client: •
open the "SNTP_Client\w32time_parameters_one_server.reg" file if only one server is master clock or "SNTP_Client\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 device defined as SNTP server in the configuration)
•
launch the "SNTP_Server\w32time_parameters_one_server.reg" or "SNTP_Server\w32time_parameters_two_servers.reg" to update the Windows registry
•
Normally, these parameters must be updated by SBUS Agency
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 18 / 128
2.3 SQL Server 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.
2.3.1 SQL Server Agent Service 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 J – 07/07/08
Identification Number: 2059660 Page: 19 / 128
2.4 SQL Server 2005
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 SQL Server Agent Service 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 J – 07/07/08
Identification Number: 2059660 Page: 20 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 21 / 128
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:
2.4.2 Russian Report Templates In addition of the Windows language (set as Russian), it is necessary to choose the "Cyrillic_General" SQL collation during the Windows SQL Server 2005 installation.
Uncheck "Case – sensitive", and check "Accent – sensitive"
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 22 / 128
2.5 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.
2.5.1 Settings for DCOM 1.
Run "dcomcnfg.exe" application from Run window typing "dcomcnfg" to configure permissions.
2.
Go to Default Properties Tab, and set "Default Authentication Level" to "Connect" as below:
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 23 / 128
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.
Go to Default Security Tab:
4.
Click on "Edit Default" in "Default Access Permissions"
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 24 / 128
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 users names, set Type of Access to "Allow Access", then click on OK
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660
Page: 25 / 128
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
6.
Click on "Edit Default" in "Default Launch Permissions"
7. For all users names, set Type of Access to "Allow Launch", then click on OK 8.
Click on "Edit Default" in "Default Configuration Permissions"
9.
For all users names, set Type of Access to "Full Control", then click on OK
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 26 / 128
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. Go to "Application" Tab, search for "S2K.OpcServer" application, select it and click on "Properties" button
11. On "General" tab, set "Authentication Level" to "Default":
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 27 / 128
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. On "Security" tab, select "Use default access permissions", "Use default launch permissions" and "Use default configuration permissions":
13. On "Identify" tab, select "The interactive user", then click on OK:
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 28 / 128
14. Do the same for "SCADA 2000 CS2KAlarmServer" application, for "General", "Security" and "Identify" tab
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. Do the same for "SCADA2000 Server.exe" application, for "General", "Security" and "Identify" tab 16. On "Location" tab, select "Run application on this computer":
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 29 / 128
17. Do the same for "USDATA Trend Datasource Server" application, for "General", "Location" and "Security" tab
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. On "Identify" tab, select "The launching user"
2.5.2 Deactivation of "Error Reporting" In order to deactivate the “Error reporting” Microsoft functionality for Windows 2000, do the following actions. To proceed deactivation, go to "Control panel" and choose "System". Open the "Advanced" tab and choose "Error reporting 1.
Run "drwtsn32 - i" application from Run window to make sure Dr Watson is launched
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 30 / 128
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.
Run "drwtsn32" application from Run window to visualize the parameters of Dr Watson
Untick "Visual Notification" and "Sound Notification", then click on "OK"
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 31 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 32 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 33 / 128
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660
Page: 34 / 128
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.09" 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. If a version of SBUS Agency is installed, uninstall it 3. Install SBUS Agency, see § 8 4. Launch SMT-R3_K.00.09.exeto install SMT application 5. 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 J – 07/07/08
Identification Number: 2059660 Page: 35 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 36 / 128
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. 48.K" folder you will find : •
the SCE_448.K.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.48.K.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.07M 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 M4RC63M\M4RC63M_setup.exe (in OI G.03.07M 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 J – 07/07/08
Identification Number: 2059660 Page: 37 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 38 / 128
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.70” folder you will find : •
the Computer_B4.70.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.70.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 J – 07/07/08
Identification Number: 2059660 Page: 39 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 40 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 41 / 128
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 J – 07/07/08
: tffs=0,0 :0 : : /flash/bin/vxWorks : : CR : : 0.0.0.0 : Identification Number: 2059660 Page: 42 / 128
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 J – 07/07/08
: tffs=0,0 :0 : : /flash/bin/vxWorks
CR CR CR Identification Number: 2059660 Page: 43 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 44 / 128
6.5 Configuration download load into the C264
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
From the CMT, you can download (only for CPU3) into the C264:
The Database of the computer only
The Databag (mpc file) of the project configuration only
The Databag (mpc file) of the project configuration and the Database of the computer
Before the download action, you have to select a Database Version (zip file). The mpc and the zip files must be in the same directory.
6.6 Telnet from CMT The "Telnet" button from the CMT tool launches the default Windows Telnet client on the operator PC. Telnet is connected to the selected computer. This tool asks for a login "c264" and a password "areva264". This login and this password are the same for each Computer.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 45 / 128
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.25.1" folder you will find : •
the GTW_4.25.1.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. If a previous version of gateway application is installed, uninstall it 2. If a previous version of SBUS Agency is installed, uninstall it 3. Install SBUS Agency, see § 8 4. Launch GTW_4.25.1.exe to install gateway application 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 J – 07/07/08
Identification Number: 2059660 Page: 46 / 128
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.1 Hopf 6039 board If there is an HOPF 6039 board and if the user wants that the GTW updates date/time received from SCADA to the HOPF board, a registry key must be declared. This functionality is used only for following SCADA protocols : T101, DNP3 and CDCII. The HOPF 6039 board has an IRIG-B output that can be connected to a C264.
T101 protocol : [HKEY_CURRENT_USER\Software\alstom\Te\T101\Protx_COMy\Configuration] Key: "Hopf_present" - This indicates if a HOPF 6039 is present or not : 0 not present ; 1 : present
DNP3 protocol : [HKEY_CURRENT_USER\Software\Areva\Te\Dnp3\Protx_COMy\Configuration] Key: "Hopf_present" - This indicates if a HOPF 6039 is present or not : 0 not present ; 1 : present
CDCII protocol : [HKEY_CURRENT_USER\Software\Areva\Protocol\CDCII\protocolx.com] Key: "cdcii_Hopf_present" - This indicates if a HOPF 6039 is present or not : 0 not present ; 1 : present
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 47 / 128
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.11" folder you will find : •
the Agency_V4.11.exe file which allows the Station Bus application installation
1. Uninstall the previous agency 2. Launch Agency_V4.11.exe to install the Station Bus application as described below
In the “License agreement” window, click on “I accept the agreement”, then on “next”
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 48 / 128
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 in the "Select Destination Location", define the installation folder and click on "next" (the default installation folder is C:\Program Files\Areva\PACIS)
In the "Select Components" window, select the chosen components to install (XP/2000 Install or XP embedded)
In the "Select Start Menu Folder" window, select where the shortcut to launch the Agency will be available (in PACiS folder by default) AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 49 / 128
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. Install WinPcap software, during the same setup of SBUS Agency
4. Reboot the PC
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 50 / 128
Note1: The agency must be installed on each PC which supports the OI server, the SMT, and the 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.
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.
VisualNotification = 0
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 51 / 128
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.
Auto = 1 Debugger = drwtsn32 –p %Id –e %Id -g
8.2 Use SBUS Agency file as dll 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.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 52 / 128
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 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 J – 07/07/08
Identification Number: 2059660 Page: 53 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 54 / 128
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 J – 07/07/08
•
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: 55 / 128
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 J – 07/07/08
IED
Identification Number: 2059660 Page: 56 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 57 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 58 / 128
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. CONFIGURATION INFORMATION
10.1 SCE Configuration 1) Measurement format The # cannot be used in decimal format, only 0 is allowed.
2) 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. 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 J – 07/07/08
Identification Number: 2059660 Page: 59 / 128
3) 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 J – 07/07/08
Identification Number: 2059660 Page: 60 / 128
4) 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.
5) GTW: Gateway ports : New protocol type: V35 ACKSYS-MCX •
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
On GTW-PC, a new board "V35 ACKSYS-MCX" has been added on Gateway port (attribute protocol type):
Identification Number: 2059660 Page: 61 / 128
6) 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
7) 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 J – 07/07/08
Identification Number: 2059660 Page: 62 / 128
8) 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").
9) 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 J – 07/07/08
Identification Number: 2059660 Page: 63 / 128
10) 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 J – 07/07/08
Identification Number: 2059660 Page: 64 / 128
11) 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 Blinking active indicator : a filter or a sorting criteria is currently applied
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 65 / 128
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) 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.
13) C264: Modbus protocol: Micom S40 A new IED type has been added for MODBUS acq type: Micom S40
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 66 / 128
14) C264: Alarm LED 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.
In SCE, the relation “has state displayed on” (allowing to associate a datapoint to a led) is modified : •
a new attribute “led behaviour” allows to choose the behaviour of the led : state / alarm
•
if “led behaviour” is equal to “state”, the 3 existing attributes (led status for set state / led status for reset state / led status for invalid state) are displayed
•
if “led behaviour” is equal to “alarm”, a new attribute “led status for transient datapoint” is displayed. It allows to choose the led behaviour for transient datapoint : ON / BLINKING (default value = ON)
SPS Datapoint:
DPS Datapoint:
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 67 / 128
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) 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 J – 07/07/08
Identification Number: 2059660 Page: 68 / 128
16) 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:
17) GTW: GTW timestamp at connection A new attribute has been added at GTW level, "GTW timestamp at connection" to timestamp the "unknown" Datapoint states at the disconnection of an equipment from IEC61850 and also at the re-connection: •
No (default value): Timestamp at time of the last state of the Datapoint
•
Yes: Timestamp at the time of the disconnection and at the time of the re-connections
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 69 / 128
18) PACiS OI: Buffer report 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 entry has been added on Scs Object: "has for buffered report client: OI server". If this entry is added on Scs, the user has to affect defined the name of OI server that is considered as receiver of Buffer reports.
19) GTW: DNP3 protocol: Measurement sent as counter For DNP3 protocol, a new attribute has been added at GTW MV addr. level, "defined as counter" to send the measurement to the protocol as a counter: •
No (default value): Measurement sent as a measurement
•
Yes: Measurement sent as a counter
20) GTW: CDC II protocol: Measurement sent as counter For CDCII protocol, to send a measurement as a counter, the SQN number must be between 64 and 95.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 70 / 128
21) SCE: Synchro SNTP by third device The Master Clock can be a C264 or a third party device.
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 can defined in the SCE 2 IP Address for Master Clock device. The master clock is now defined at the Scs level :
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 71 / 128
22) C264: Local Alarm Acknowledgement
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
In addition to the Global Alarm Acknowledgement SPS, a Local Alarm Acknowledgment SPS can be defined on a per C264 basis (i.e. one per C264). This SPS can be wired, managed by an automation or associated to a control. When this SPS is configured in a C264, the "Global Alarm Acknowledgement" SPS is no more taken into account by this C264. When this SPS is SET, all C264 alarms are immediately acknowledged. This SPS cannot be transmitted on the Station Bus network (i.e. it remains local to the C264).
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 72 / 128
10.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.
10.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.
10.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 J – 07/07/08
Identification Number: 2059660 Page: 73 / 128
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.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.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 74 / 128
10.3 Time 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.
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. All PC (PACiS OI, PACiS GTW, PACiS SMT) must be configured with the same time zone, normally country timezone.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 75 / 128
10.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 J – 07/07/08
Identification Number: 2059660 Page: 76 / 128
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. ISAGRAF AUTOMATION
11.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 J – 07/07/08
Identification Number: 2059660 Page: 77 / 128
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 J – 07/07/08
Identification Number: 2059660
Page: 78 / 128
11.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 J – 07/07/08
Identification Number: 2059660 Page: 79 / 128
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. 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 J – 07/07/08
Identification Number: 2059660 Page: 80 / 128
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 TWIN SERVER SAFE FUNCTION The copy of persistence files from Master to Backup OI Server has been deactivated. So, there is no need to modify the registry key of the Twin Server Safe function. After a switch of OI Client connected to the OI Server Backup, the user has to acknowledge the alarms.
13.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
4.
Memos are shared between the 2 OI Servers
5.
Profiles and passwords are shared between the 2 OI Servers
6.
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 J – 07/07/08
Identification Number: 2059660 Page: 81 / 128
13.2 Configuration and settings 13.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
13.2.2 Setting Twin Server Safe 13.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 cmd and dat files for Twin server safe function 4) Start PACiS OI Server 5) Download Database from SMT 6) Switch Database from SMT 7) Start PACiS OI Client 8) When OI Client configuration is the good one, stop PACiS OI Client 9) Modify connection to servers 10) Start PACiS OI Client
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 82 / 128
13.2.2.2 New Database On both PCs, do the following actions (see below for details):
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) Download Database from SMT 2) Switch Database from SMT 3) When OI Client configuration is the good one, stop PACiS OI Client 4) Modify connection to servers 5) Start PACiS OI Client
13.2.3 Modify files for Twin servers safe function 13.2.3.1 On Master OI Server: •
"Servers.dat" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\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 : "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\ backup_historian.cmd" Replace MASTER by the PC name of the Master OI Server Save file
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 83 / 128
•
"Restore_historian.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\ restore_historian.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 Historian backup to REMOTE.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy Historian backup to REMOTE.cmd " Replace REMOTE by the PC name of the Remote OI Server Save file •
"Copy persistence to REMOTE.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy persistence to REMOTE.cmd " Replace REMOTE by the PC name of the Remote OI Server Save file
13.2.3.2 On Remote OI Server: •
"Servers.dat" file:
Edit (Notepad) file : "C:\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 : "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ backup_historian.cmd" Replace REMOTE by the PC name of the Remote OI Server Save file AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 84 / 128
•
"Restore_historian.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ restore_historian.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 Historian backup to MASTER.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy Historian backup to MASTER.cmd " Replace MASTER by the PC name of the Master OI Server Save file •
"Copy persistence to MASTER.cmd" file:
Edit (Notepad) file : "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy persistence to MASTER.cmd " Replace MASTER by the PC name of the Master OI Server Save file
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 85 / 128
13.2.4 PACiS OI Client – connection to servers
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
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. On Master OI Server : •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy servers to LocalWorkspace.cmd" file
On Remote OI Server : •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy servers to LocalWorkspace.cmd" file
On PACiS OI Client Standalone : •
Copy "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\servers.dat" file of Master OI Server to "C:\LocalWorkspace\Config files\" of the PACiS OI Client
WARNING : the modification of the "servers.dat" file must be done after each download / switch of a database.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 86 / 128
13.3 Failure cases
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.3.1 Loss of Master PC
N° Actions 1
Master PC
Remote PC
Restart
Acknowledge Alarms
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)
13.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
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 87 / 128
13.3.3 Backup Historian Data Base Backup Historian Database on Remote 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 "C:\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 "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\ backup_historian.cmd" file
This procedure create a backup file into C:\BACKUP directory.
13.3.4 Restore Historian Data Base Restore Historian Database on Remote Server •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\ restore_historian.cmd" file
Restore Historian Database on Master Server •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\ restore_historian.cmd" file
13.3.5 Copy Historian backup file Copy Historian backup file from Remote Server to Master Server •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy Historian backup to MASTER.cmd " file
Copy Historian backup file from Master Server to Remote Server •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy Historian backup to REMOTE.cmd " file
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 88 / 128
13.3.6 Copy Persistence files Copy Persistence files 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 "C:\TWIN_SERVER_SAFE_FILES_FOR_REMOTE\Copy persistence to MASTER.cmd " file
Copy Persistence files from Master Server to Remote Server •
Execute "C:\TWIN_SERVER_SAFE_FILES_FOR_MASTER\Copy persistence to REMOTE.cmd " file
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 89 / 128
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. 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 J – 07/07/08
Identification Number: 2059660 Page: 90 / 128
14.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 J – 07/07/08
Identification Number: 2059660 Page: 91 / 128
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..65535]".
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. 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 J – 07/07/08
Identification Number: 2059660 Page: 92 / 128
14.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 J – 07/07/08
Identification Number: 2059660 Page: 93 / 128
3 – From the gateway, launch the "Edit relation" in the contextual menu, click on the tab "To", click on the item "manages: Bay [0..65535]".
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 J – 07/07/08
Identification Number: 2059660 Page: 94 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 95 / 128
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, then in the bottom listbox , select the GTW, then Click on "Set" button (a message box is displayed "IED model import in progress, please wait")
-
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.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 96 / 128
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
5 – On GTW_IEC, change the short name and long name of the Operating mode of the GTW_IEC. These names must not be the same as name of Operating mode of the GTW on the lower network.
6 - Change the "short name", "long name", "network name" and "TCP/IP address" of OI server to be compatible with upper network. 7 - Fill the relation between OI server and IEC/IEC gateway (named "has for UCA2/IEC server"). 8 - Check in and generate the upper database before completing the rest of the configuration.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 97 / 128
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. 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 J – 07/07/08
Identification Number: 2059660 Page: 98 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 99 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 100 / 128
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. 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 J – 07/07/08
Identification Number: 2059660 Page: 101 / 128
16.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 J – 07/07/08
Identification Number: 2059660 Page: 102 / 128
16.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.
16.2.1 Deactivation of Security Center Start>Settings>Control Panel
Click on "Performance and Maintenance"
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 103 / 128
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 J – 07/07/08
Identification Number: 2059660
Page: 104 / 128
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.
16.2.2 Deactivation of Firewall From "Components Services", select "Windows Firewall/Internet Connection:
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 105 / 128
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.
16.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 J – 07/07/08
Identification Number: 2059660 Page: 106 / 128
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 J – 07/07/08
Identification Number: 2059660
Page: 107 / 128
16.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 J – 07/07/08
Identification Number: 2059660 Page: 108 / 128
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 J – 07/07/08
Identification Number: 2059660
Page: 109 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 110 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 111 / 128
16.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:
16.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 J – 07/07/08
Identification Number: 2059660 Page: 112 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 113 / 128
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:
16.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 J – 07/07/08
Identification Number: 2059660 Page: 114 / 128
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.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 J – 07/07/08
Identification Number: 2059660 Page: 115 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 116 / 128
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.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 J – 07/07/08
Identification Number: 2059660 Page: 117 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 118 / 128
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 J – 07/07/08
Identification Number: 2059660 Page: 119 / 128
16.2.10 PACiS OI: Socket Limitation Extension software In Microsoft Windows XP SP2 and laters, there is a limitation of 10 concurrent TCP connection attempts.
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
This limitation is prejudicial to PACIS OI connection performances. To extend this limit use the 'EvID4226Patch.exe' software included in the “SocketLimitationExtension” folder of delivery of PACiS OI. We recommend to change the limit to 200. Follow the steps below for doing this: 1. Execute the 'EvID4226Patch.exe’ software. A command prompt window will be shown. 2. You will then be asked some questions. “Do you really want to change the limit to 10?” Type ‘C’ (C=Change limit).
3.
“Please enter the number of concurrent half-open connections” Type ‘200’
4. “Do you really want to change the limit to 200?” Type ‘Y’ (Y=Yes)
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 120 / 128
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. “May these files be renamed until end of patching?” Type ‘Y’ (Y=Yes)
6. A countdown (15 seconds) will be started for rechecking the files. During this countdown a Windows File Protection popup might appear. You will be requested to insert the Service Pack CD. Don’t insert the CD. Just click on ‘Cancel’.
7. Another popup will appear asking you if you are sure to keep unrecognized file versions. Click on ‘Yes’.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 121 / 128
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.
Note: The countdown and the program execution in the command prompt window don’t wait for the Windows File Protection pop-ups closing. 8. The program execution in the command prompt window will finish and you will be asked to press any key to exit. Press a key and reboot the PC to finish the installation.
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 122 / 128
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. 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.
17.1 How to use the configure a report from the SCE First you need to configure a button with a “Run Report” launch action link as shown below:
The “Application name” and “Export format type” attributes are mandatory. The "Application name" corresponds to the report filename (don not include the file extension). The " Export format type" is only Excel 8.0 (xls file).
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 123 / 128
17.2 How to use a report created before PACiS V4.4.4
CONFIDENTIAL. All rights reserved. AREVA. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
The former "Run Appli" Launch action with specific Application name:Report1 to Report10 will be transformed automatically into "Run Report" with the same Application name. Be careful: for this upgrade, the name of application (Report1 to Report10) must be the same into both languages of Database. Do not use anymore "Run Appli" to create a specific report. Use the "Run Report" action. If the report file contains the field "@FileTimeToString", this report must be updated as follows: 1. Open the report with Crystal Reports. Sometimes this pop-up window appears:
Set these information:
-
Server: set your PACiS OI Server name
-
UserID: 'sa'
-
Password: nothing
-
Database: Choose 'Historian'
2. Check if the field "@FileTimeToString". If NO, no migration is mandatory (close report). If YES, continue with the following steps:
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 124 / 128
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. Open "Field Explorer": menu "Insert\Field Object"
4. On the item "SQL expression Fields", click right button. A pop-up menu will be displayed 5. On this pop-up menu, choose "New …" item
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 125 / 128
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. On the pop-up window displayed, write the "GetEventFileTimeStr". Then click on OK button.
SQL
expression
name:
7. On the new window (see below), add the following formula line: CAST (S2KEventReport_View.EventFileTime AS NVARCHAR)
8. Check there are no errors by clicking on the "Check syntax" button
9. Click on the Save button, then exit the window
10.
Close the "Field Explorer" window
11.
On the field "@FileTimeToString", click right and choose "Edit Field Object" item
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 126 / 128
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.
Change the following formula line to the new format:
Old: FiletimeToString2 ({S2KEventReport_View.LocaleID},{S2KEventReport_View.EventFileTime},"","hh:m m:ss tt") New: FiletimeToString3 ({S2KEventReport_View.LocaleID},{%GetEventFileTimeStr},"","hh:mm:ss tt")
13.
Check that there are no errors by clicking on the “Check syntax" button, click on Save and exit the window
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 127 / 128
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.
Click on Save icon to save your new report updated. Then exit the Crystal Report software
AREVA PACIS V4.4 ReadMe RM – Issue J – 07/07/08
Identification Number: 2059660 Page: 128 / 128
View more...
Comments
