L2 V4 01 System Devices Configuration E 01

(1)

PACiS System Devices

Configuration

PCL

PACiS Configuration Training

CS&P

(2)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(3)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(4)

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

Periodic SQL Historian DB backup

15 Note : use OI configured in starting database

Follow Good Practice for

addressing

(5)

Basic = System Infos + IEC Mapping

Note : use OI configured in starting

database, all system information are

already configured

List of System Information :

Operating Mode,

Synchronisation Status, ...

(6)

Possible sons

Klaxon for audible alarm

Serial Printer

Sequence of Events / System

Log Book

Printer Name as installed on the

PC (spool name)

for main and backup

• Printer

Used when main printer breaks down

during starting of backup printer

Used during ordering

process of dated events

(7)

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

uses the buzzer

Note : Relation “warns audibly” (gives an audible warning) to determine which

alarms are triggering the klaxon

(8)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(9)

Under SCS/Ethernet Network

Add from Object Entry window

PACiS OI Client Attributes

Network name + IP@

same if installed on same PC as

OI Server

Follow Good Practice for

addressing

(10)

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

Link Status :

Status of the Link between OI Client and

OI server

Link to OI Server

- all clients are linked with PACiS

OI Server Main or Backup.

- At least 1 OI Client has to be

connected on each OI Server.

Link to graphic part

the client will show the views

configured under the chosen

workspace

(11)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(12)

Under SCS/Ethernet Network

Add from Object Entry window

Note1 : use C264 configured in starting database

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

(13)

General Tab

Network name + IP@

Computer Name

IRIG-B signal or not

80TE=C264 / 40TE=C264C

Follow Good Practice for

addressing

(14)

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 i l t e r i n g t i m e

t0 t₁ t2

D e b o u c i n g t i m e

Debouncing / Filtering => signal

validation

Timetag => t0 or t2 (configurable)

(15)

Measurements Tab

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

Long period = N x short period

AI board acquisition cycle

Debouncing / Filtering => signal

validation for Digital Measurements

CT/VT board acquisition frequency

(neighbourhood of 0)

MV transmission cycle on SBUS and

LHMI

Note 2 : too small transmission periods values has strong impact on SQL

(16)

Counter Tab

Note : Applicable for single or double counters

Debouncing / Filtering => signal

validation for counted Digital Input

Miscellaneous Tab

Avoid endless C264 reboot on fault

detection, define a number of faults

acceptable during a period.

(17)

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

I/O Boards :

Naming Good Practice :

Slot#_<board type>_<board nb>

IEC 61850 Mapping

Created by Automatic Addressing

function

PLC Object

C264 Automations

(18)

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

List of System Information :

Operating Mode,

Synchronisation Status, ...

Note : use C264 configured in starting

database, all system information are

already configured

(19)

Possible sons = Object Entry Window

Hardware

LBUS

per protocol

TBUS

Local C264 printer

Add / Configure I/O board

Note : another method is to copy/paste existing board

(20)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(21)

Under SCS/Ethernet Network

Add from Object Entry window

Note1 : use GTW configured in starting database

PACiS GTW Attributes

Network name + IP@

Follow Good Practice for

addressing

(22)

Basic = System Infos + 8 serial ports + IEC Mapping

List of System Information :

Operating Mode,

Synchronisation Status, ...

Note : use GTW configured in starting

1 to 4 protocols with the

relevant SCADA mapping

8 serial communication ports

(23)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(24)

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

(25)

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 :

_{LAN :}

(26)

Central Archive => MPS (under OIS)

PACiS OI Redundancy Status => MPS (under OIS)

(27)

PACiS OI Server Configuration

PACiS OI Client Configuration

C264 Configuration

PACiS Gateway Configuration

Labels in Datapoint profiles

Devices Redundancy

(28)

Create Redundant C264

• Select C264 and “Create Backup”

• Redundant C264 parameters

(29)

Create Redundant OI Server

• Select OI Server and “Create Backup”

• Redundant OI Server parameters

(30)

On PACiS 4.6.0, Hot redundancy principle :

• OI Client is connected to

“preferred” OI Server

. If server not available

it will immediately try connect to the other one.

Client B

Client A Client C

IEC 61850 Station Bus Server 1 Server 2

SQL database SQL database

• Both OI server perform

DP acquisition simultaneously

. There is a

consolidating mechanism

insuring all data are the same on both.

(31)

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

itself)

to OI Master

which will manage the controls.

(32)

• 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

(directly

connected to itself) as the other Standalone OI; but in that case

Control

Uniqueness is done at C264 level.

- print events on connected SOE printers

• Performances (typical switching time):

Less than 60s

Ethernet disconnection

Less than 20s

Application stop

Less than 20s

PC power off

OI Client switching time

OI server failure

(33)

Server 1

Server 2

START-UP

WAIT

STANDALONE

SLAVE

MASTER

Both OI are connected on Ethernet and visible.

Server 1

Server 2

MASTER

SLAVE

GOING TO

STANDALONE

PC halted

PC start-up

START-UP

MASTER

SLAVE

OI Master shuts down then restarts

OI is proceeding consolidating messages before

going to Standalone.

(34)

One OI is not connected and reconnects.

Server 1

Server 2

START-UP

STANDALONE

Ethernet connexion

MASTER

SHUTDOWN

START-UP

SLAVE

Case 1 : no OI client connected on OI server 1

Server 1

Server 2

START-UP

STANDALONE

Ethernet connexion

SHUTDOWN

START-UP

SLAVE

MASTER

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)

Fault Tolerance automation : principle of MASTER/SLAVE election

1. The 1st server that starts is MASTER

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

b.

The quantity of connected clients

c.

The first one configured in SCE

The client connection to preferred server principle and the

MASTER/SLAVE election have no correlation

(36)

SQL consolidation

Objective : ensure both OI servers Historian database are in line

How :

At SQL level

only

Every

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

(37)

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.

(38)

Buffered reports is used to retrieve max 1000 events stored in C264 in

case of C264 disconnection from OI Server (PACiS GTW

DOES NOT

support buffered reports)

Add relation under SCS : Has for buffered report client : <OI server>

Functionality can be tested on OI event viewer (printer is depending on

its own buffer)

A Buffer overflow DP is reached in that case.