l2 v4 01 system devices configuration e 01

8/20/2019 L2 V4 01 System Devices Configuration E 01

1/38

PACiS System Devices

Configuration

PCL

PACiS Configuration TrainingPACiS Configuration TrainingPACiS Configuration TrainingPACiS Configuration Training

CS&PCS&PCS&PCS&P – –– – Support Team Support Team Support Team Support Team


2/38

Schneider Electric 2- CS&P – System Devices Configuration – E01

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

• Content


3/38






Devices Redundancy

• Content


4/38


Under SCS/Ethernet Network

Add from Object Entry window

PACiS OI Server Attributes

Network name (Never HMI) + IP@

MV computation period

Max number of presence

days for event/value in SQLHistorian database

Periodic SQL Historian DB backup

Good Practice

155

Note : use OI configured in starting database

Follow Good Practice for

addressing

• Add / Configure PACiS OI Server


5/38


Basic = System Infos + IEC Mapping

Note : use OI configured in starting

database, all system information arealready configured

List of System Information :Operating Mode,Synchronisation Status, ...

IEC 61850 Mapping

• PACiS OI Server Sons


6/38


Possible sons

Klaxon for audible alarm

Serial Printer

Sequence of Events / System

Log Book

Printer Name as installed on thePC (spool name)for main and backup

• Printer

Used when main printer breaks downUsed when main printer breaks downUsed when main printer breaks downUsed when main printer breaks downduring starting of backup printer during starting of backup printer during starting of backup printer during starting of backup printer

Used during orderingUsed during orderingUsed during orderingUsed during orderingprocess of dated eventsprocess of dated eventsprocess of dated eventsprocess of dated events



7/38


• Klaxon

Klaxon action (immediate/defer) and

acknowledgement (auto/manu).

Klaxon can be executed on one SPC in

one C264 (horn).If not configured => PACiS OI Server PCuses the buzzer

Note : Relation “warns audibly” (gives an audible warning) to determine whichalarms are triggering the klaxon

Note 2 : The SPC must be direct execute, without dependency, withoutinterlock, with “on” and “off” orders possibility.



8/38






Devices Redundancy

• Content


9/38




PACiS OI Client Attributes

Network name + IP@same if installed on same PC asOI Server


addressing

• Add / Configure PACiS OI Client


10/38


Basic = System Infos + Relation to OI Server + Relation to graphic part

Link Status :Status of the Link between OI Client andOI server

Link to OI Server- all clients are linked with PACiSOI Server Main or Backup.- At least 1 OI Client has to be

connected on each OI Server.Link to graphic partthe client will show the views

configured under the chosenworkspace

• PACiS OI Client Sons and Relations


11/38






Devices Redundancy

• Content


12/38




Note1 : use C264 configured in starting database

Note2 : create new C264 by copy/paste of existing one

• Add / Configure MiCOM C264


13/38


General Tab

Network name + IP@

Computer Name

IRIG-B signal or not

80TE=C264 / 40TE=C264C


addressing

• MiCOM C264 Attributes


14/38


BI Filtering Tab

Note : used for SPS, DPS and MPS acquisition on DI board

Toggling applied on validated signal

Toggling parameters

Debouncing / Filtering => signal

validation

F ilt e r in g tim e

t 0 t 1t 2

D e b o u c in gt im e

Debouncing / Filtering => signalvalidation

Timetag => t0 or t2 (configurable)



15/38


Measurements Tab

Note 1 : Transmission periods are used if MV is declared as “periodic”

Long period = N x short period

AI board acquisition cycle


validation for Digital Measurements

CT/VT board acquisition frequency(neighbourhood of 0)

MV transmission cycle on SBUS andLHMI

Note 2 : too small transmission periods values has strong impact on SQLHistorian database filling => default values are too small



16/38


Counter Tab

Note : Applicable for single or double counters


validation for counted Digital Input

Miscellaneous Tab

Avoid endless C264 reboot on faultdetection, define a number of faults

acceptable during a period.



17/38


Basic = System Infos + 3 boards (CPU,BIU,GHU) + IEC Mapping

I/O Boards :Naming Good Practice :

Slot#__

IEC 61850 Mapping

Created by Automatic Addressingfunction

PLC Object

C264 Automations

• MiCOM C264 Sons


18/38


Basic = System Infos + 3 boards (CPU,BIU,GHU) + IEC Mapping


Note : use C264 configured in startingdatabase, all system information arealready configured

• MiCOM C264 Sons


19/38


Possible sons = Object Entry Window

HardwareLBUS per protocol

TBUS

Local C264 printer

Add / Configure I/O board

Note : another method is to copy/paste existing board

Physical Board Number Relation made by automatic @(to remove when duplication)

• MiCOM C264 Sons


20/38






Devices Redundancy

• Content


21/38


Under SCS/Ethernet NetworkAdd from Object Entry window

Note1 : use GTW configured in starting database

PACiS GTW Attributes

Network name + IP@

Follow Good Practice foraddressing

• Add / Configure PACiS Gateway


22/38


Basic = System Infos + 8 serial ports + IEC Mapping


Note : use GTW configured in startingdatabase, all system information arealready configured IEC 61850 Mapping

1 to 4 protocols with the

relevant SCADA mapping

8 serial communication ports

• PACiS Gateway Sons


23/38






Devices Redundancy

• Content


24/38


All Devices Operating Mode (OI, C264, GTW) => MPS

MiCOM C264 Boards status => MPS

Note 1 : TEST Mode N/A for OI and GTW

Note 1 : Applicable for all kind of boards

Note 2 : Special status Missing = in configuration not in rack

Too Many = in rack not in configuration OK Empty = used at SMT only

Note 2 : Useful for graphical animation

• System Information Labels in Profiles


25/38


ISaGRAF Status => MPS (under C264/PLC)

PACiS OI Printer Status (parallel or LAN) (SOE/SLB) => MPS

Note : Not Activated = No ISaGRAF configured

Cycle too long = cycle > 2s Queue Overflow = ISaGRAF overflow

Note 2 : N/A for C264 printer

Parallel :Parallel :Parallel :Parallel : LAN :LAN :LAN :LAN :



26/38


Central Archive => MPS (under OIS)

PACiS OI Redundancy Status => MPS (under OIS)



27/38






Devices Redundancy

• Content


28/38


Create Redundant C264

• Select C264 and “Create Backup”

• Redundant C264 parameters

• Redundant MiCOM C264


29/38


Create Redundant OI Server

• Select OI Server and “Create Backup”

• Redundant OI Server parameters

• Redundant PACiS OI Server


30/38


On PACiS 4.6.0, Hot redundancy principle :

• OI Client is connected to “preferred” OI Server. If server not availableit will immediately try connect to the other one.

Client BClient A Client C

IEC 61850 Station Bus

Server 1 Server 2

SQL database SQL database

• Both OI server perform DP acquisition simultaneously. There is aconsolidating mechanism insuring all data are the same on both.

• Hot Redundancy in PACiS OI Server


31/38


• Each OI server is managing its own system DP. These are not

consolidating because each server is aware of status of the other one.

• Master OI can :- acquire DP from IEC servers.- be connected to OI Client.- perform archives (Historian) and manage alarms.- accept and manage controls from any OI Client (directly

connected to itself or connected to OI Slave).- print events on SOE printers

• Slave OI can :

- acquire DP from IEC servers.- be connected to OI Client.- perform archives (Historian) and manage alarms.

- propagate controls from its OI Client (directly connected toitself) to OI Master which will manage the controls.


H R d d i PACiS OI S


32/38


• Standalone OI can :- acquire DP from IEC servers.- be connected to OI Client.

- perform archives (Historian) and manage alarms.- accept and manage controls from its OI Client (directlyconnected to itself) as the other Standalone OI; but in that case ControlUniqueness is done at C264 level.

- print events on connected SOE printers

• Performances (typical switching time):

Less than 60sEthernet disconnection

Less than 20sApplication stop

Less than 20sPC power off

OI Client switching timeOI server failure


H t R d d i PACiS OI S


33/38


Server 1 Server 2

START-UP START-UP

WAITSTANDALONE

SLAVEMASTER

Both OI are connected on Ethernet and visible.

Server 1 Server 2

MASTER SLAVE

GOING TO

STANDALONE

STANDALONE

PC halted

PC start-up

START-UP

MASTERSLAVE

OI Master shuts down then restarts

OI is proceeding consolidating messages beforegoing to Standalone.




34/38


One OI is not connected and reconnects. One OI is not connected and reconnects.

Server 1 Server 2

START-UP START-UP

STANDALONESTANDALONE

Ethernet connexion

MASTER

SHUTDOWN

START-UP

SLAVE

Case 1 : no OI client connected on OI server 1

Server 1 Server 2

START-UP START-UP

STANDALONESTANDALONE

Ethernet connexion

SHUTDOWN

START-UP

SLAVEMASTER

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

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




35/38


Fault Tolerance automation : principle of MASTER/SLAVE election

1. The 1st server that starts is MASTER2. In case of Ethernet reconnection, the criteria for MASTER election

are, from highest priority to lowest :

a. There is a control in progress on one serverb. The quantity of connected clientsc. The first one configured in SCE

The client connection to preferred server principle and theMASTER/SLAVE election have no correlation




36/38


SQL consolidation

Objective : ensure both OI servers Historian database are in line

How :

At SQL level onlyEvery 2 minutes (based on clock time : 8h00, 8h02, 8h04, …) :

• Compare both databases• Fix discrepancies (if any)• Tag every consolidated event

• Next consolidation starts from 1st event not tagged


Hot Redundancy in PACiS OI Server


37/38


On PACiS 4.6.0, Hot redundancy configuration :1. Preferred server of OI Client is chosen using relation “Has for HMI

server ”2. Good Practice is to select at least 1 OI Client per OI Server .3. Files “servers.dat” are automatically created by SCE during

generation. There is no need to manually install it after DB switch.


• Buffered Reports for PACiS OI Server


38/38


Buffered reports is used to retrieve max 1000 events stored in C264 incase of C264 disconnection from OI Server (PACiS GTW DOES NOTsupport buffered reports)

Add relation under SCS : Has for buffered report client :

Functionality can be tested on OI event viewer (printer is depending onits own buffer)

A Buffer overflow DP is reached in that case.

• Buffered Reports for PACiS OI Server

l2 v4 01 system devices configuration e 01

Documents