PACiS V4.4 ReadMe_J

(1)

C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n .

AREVA PACiS

PACiS V4

README

PACiS V4.4

DISTRIBUTION Confidentiality Category Restricted Normal Control Category

Controlled Not Controlled

Identification number Identification letters Issue T r a n s m i s s i o n & D i s t r i b u t i o n

2059660 RM J

AREVA T&D Protection & Contrôle, Avenue de Figuières – BP75

(2)

(3)

AREVA PACIS V4.4 Identification Number: 2059660 C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . APPROVAL SIGNATURES

NAME POSITION DATE SIGNATURE

JM. BOISSET PACiS PROJECT

MANAGER

M. VERNEY R&D VALIDATION &

SUPPORT GROUP MANAGER

B. NAL PACiS QUALITY

(4)

C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . 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

(5)

AREVA PACIS V4.4 Identification Number: 2059660 C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n .

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

(6)

C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . 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

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

(7)

AREVA PACIS V4.4 Identification Number: 2059660 C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . 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 Adding information on

SocketLimitationExtension software (extend the number of TCP connection attempts on PACiS

(8)

AREVA PACIS V4.4 Identification Number: 2059660 C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . 10.1 OIPRINTER 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 SCE:MULTI DO IN THE SAME STEP...77

11.2 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 "LOWER" NETWORK...91

14.2 "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 HOW TO USE THE CONFIGURE A REPORT FROM THE SCE ...123

(10)

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.

(11)

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"),

(12)

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<xy> dll files.

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

(13)

2.1.2 Stand-alone OI client installation

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

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

1. During 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

(14)

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,

(15)

4. Configuration of network disconnection/ reconnection mechanism:

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 key:

"HKEY_LOCAL_MACHINE/SOFTWARE/AREVA/PACIS/Configuration".

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.

(16)

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

(17)

2.2 Windows Time service - SNTP

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

(18)

C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n . 2.2.2 Windows 2000 Directory : SNTP/W2K 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

(19)

2.3 SQL Server 2000

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"

(20)

2.4 SQL Server 2005

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:

(21)

• Click on Start button:

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

(22)

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

(23)

2.5 Windows 2000

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:

(24)

3. Go to Default Security Tab:

(25)

(26)

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"

(27)

10. Go to "Application" Tab, search for "S2K.OpcServer" application, select it and click on "Properties" button

(28)

12. On "Security" tab, select "Use default access permissions", "Use default launch permissions" and "Use default configuration permissions":

(29)

14. Do the same for "SCADA 2000 CS2KAlarmServer" application, for "General", "Security" and "Identify" tab

15. Do the same for "SCADA2000 Server.exe" application, for "General", "Security" and "Identify" tab

(30)

17. Do the same for "USDATA Trend Datasource Server" application, for "General", "Location" and "Security" tab

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

(31)

2. Run "drwtsn32" application from Run window to visualize the parameters of Dr Watson

(32)

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 »).

(33)

AREVA PACIS V4.4 Identification Number: 2059660 C O N F ID E N T IA L . A ll ri g h ts r e s e rv e d . A R E V A . P a s s in g o n a n d c o p y in g o f th is d o c u m e n t, u s e a n d c o m m u n ic a ti o n o f its c o n te n ts a re n o t p e rm it te d w it h o u t p ri o r w ri tt e n a u th o ri z a ti o n

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

(34)

(35)

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.

(36)

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.

(37)

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<xy> dll files.

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

• Install ISaGRAF workbench 4.12

• Using USB dongle, install the dongle management software: Sentinel Protection.

(38)

• 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=F9DFA82C-9A3B-40DF-B6E4-DC15E6112BBC&displaylang=en

• The ISaGraf workbench cannot be launched from the redundant computer in the

SCE. The following procedure must be applied:

• Launch the ISaGraf workbench from the PLC of the main computer in the

SCE,

• Open the "hardware architecture" window (look at the window menu), • Click on the graphical link between the ETCP network and the "config1"

equipment to select it,

• Right-click on this link and choose the "property" menu,

• Modify the IP address (i.e. replace the IP address of the main C264 with the IP address of the redundant one).