L2 V4 01 System Devices Configuration E 01
Short Description
SAS...
Description
PACiS System Devices Configuration PACiS Configuration Training CS&P – Support Team
PCL
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
2
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
3
• Add / Configure PACiS OI Server Under SCS/Ethernet Network Add from Object Entry window
Note : use OI configured in starting database
PACiS OI Server Attributes Follow Good Practice for addressing MV computation period Network name (Never HMI) + IP@ Periodic SQL Historian DB backup 15 5 Good Practice Schneider Electric - CS&P – System Devices Configuration – E01
Max number of presence days for event/value in SQL Historian database 4
• PACiS OI Server Sons Basic = System Infos + IEC Mapping
List of System Information : Operating Mode, Synchronisation Status, ... Note : use OI configured in starting database, all system information are already configured
IEC 61850 Mapping Schneider Electric - CS&P – System Devices Configuration – E01
5
• PACiS OI Server Sons Possible sons Klaxon for audible alarm
Serial Printer • Printer Sequence of Events / System Log Book Printer Name as installed on the PC (spool name) for main and backup Used during ordering process of dated events
Schneider Electric - CS&P – System Devices Configuration – E01
Used when main printer breaks down during starting of backup printer
6
• PACiS OI Server Sons • 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 Note 2 : The SPC must be direct execute, without dependency, without interlock, with “on” and “off” orders possibility.
Schneider Electric - CS&P – System Devices Configuration – E01
7
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
8
• Add / Configure PACiS OI Client Under SCS/Ethernet Network Add from Object Entry window
PACiS OI Client Attributes Follow Good Practice for addressing
Network name + IP@ same if installed on same PC as OI Server
Schneider Electric - CS&P – System Devices Configuration – E01
9
• PACiS OI Client Sons and Relations 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
Link to graphic part
- all clients are linked with PACiS OI Server Main or Backup. - At least 1 OI Client has to be connected on each OI Server.
the client will show the views configured under the chosen workspace
Schneider Electric - CS&P – System Devices Configuration – E01
10
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
11
• Add / Configure MiCOM C264 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
Schneider Electric - CS&P – System Devices Configuration – E01
12
• MiCOM C264 Attributes General Tab
Computer Name 80TE=C264 / 40TE=C264C
IRIG-B signal or not Network name + IP@ Follow Good Practice for addressing
Schneider Electric - CS&P – System Devices Configuration – E01
13
• MiCOM C264 Attributes BI Filtering Tab
Debouncing / Filtering => signal validation Toggling parameters Note : used for SPS, DPS and MPS acquisition on DI board
Debouncing / Filtering => signal validation Timetag => t0 or t2 (configurable)
F ilte r in g tim e D e b o u c in g tim e t0
t1
t2
Toggling applied on validated signal
Schneider Electric - CS&P – System Devices Configuration – E01
14
• MiCOM C264 Attributes Measurements Tab
Debouncing / Filtering => signal validation for Digital Measurements AI board acquisition cycle CT/VT board acquisition frequency (neighbourhood of 0) MV transmission cycle on SBUS and LHMI Long period = N x short period Note 1 : Transmission periods are used if MV is declared as “periodic” Note 2 : too small transmission periods values has strong impact on SQL Historian database filling => default values are too small
Schneider Electric - CS&P – System Devices Configuration – E01
15
• MiCOM C264 Attributes Counter Tab
Debouncing / Filtering => signal validation for counted Digital Input Note : Applicable for single or double counters
Miscellaneous Tab
Avoid endless C264 reboot on fault detection, define a number of faults acceptable during a period.
Schneider Electric - CS&P – System Devices Configuration – E01
16
• MiCOM C264 Sons Basic = System Infos + 3 boards (CPU,BIU,GHU) + IEC Mapping
I/O Boards : Naming Good Practice : Slot#__
IEC 61850 Mapping Created by Automatic Addressing function
PLC Object C264 Automations
Schneider Electric - CS&P – System Devices Configuration – E01
17
• MiCOM C264 Sons 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
Schneider Electric - CS&P – System Devices Configuration – E01
18
• MiCOM C264 Sons 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
Physical Board Number Schneider Electric - CS&P – System Devices Configuration – E01
Relation made by automatic @ (to remove when duplication)
19
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
20
• Add / Configure PACiS Gateway Under SCS/Ethernet Network Add from Object Entry window
Note1 : use GTW configured in starting database
PACiS GTW Attributes
Follow Good Practice for addressing Network name + IP@
Schneider Electric - CS&P – System Devices Configuration – E01
21
• PACiS Gateway Sons Basic = System Infos + 8 serial ports + IEC Mapping 8 serial communication ports
1 to 4 protocols with the relevant SCADA mapping
List of System Information : Operating Mode, Synchronisation Status, ...
IEC 61850 Mapping Schneider Electric - CS&P – System Devices Configuration – E01
Note : use GTW configured in starting database, all system information are already configured 22
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
23
• System Information Labels in Profiles All Devices Operating Mode (OI, C264, GTW) => MPS
Note 1 : TEST Mode N/A for OI and GTW Note 2 : Useful for graphical animation
MiCOM C264 Boards status => MPS 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
Schneider Electric - CS&P – System Devices Configuration – E01
24
• System Information Labels in Profiles ISaGRAF Status => MPS (under C264/PLC) Note : Not Activated = No ISaGRAF configured Cycle too long = cycle > 2s Queue Overflow = ISaGRAF overflow
PACiS OI Printer Status (parallel or LAN) (SOE/SLB) => MPS Note 2 : N/A for C264 printer Parallel :
Schneider Electric - CS&P – System Devices Configuration – E01
LAN :
25
• System Information Labels in Profiles Central Archive => MPS (under OIS)
PACiS OI Redundancy Status => MPS (under OIS)
Schneider Electric - CS&P – System Devices Configuration – E01
26
• Content
PACiS OI Server Configuration PACiS OI Client Configuration C264 Configuration PACiS Gateway Configuration Labels in Datapoint profiles Devices Redundancy
Schneider Electric - CS&P – System Devices Configuration – E01
27
• Redundant MiCOM C264 Create Redundant C264 • Select C264 and “Create Backup”
• Redundant C264 parameters
Schneider Electric - CS&P – System Devices Configuration – E01
28
• Redundant PACiS OI Server Create Redundant OI Server • Select OI Server and “Create Backup”
• Redundant OI Server parameters
Schneider Electric - CS&P – System Devices Configuration – E01
29
• Hot Redundancy in PACiS OI Server 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 A
Client B
Client C
Server 1
Server 2
SQL database
SQL database
IEC 61850 Station Bus
• Both OI server perform DP acquisition simultaneously. There is a consolidating mechanism insuring all data are the same on both.
Schneider Electric - CS&P – System Devices Configuration – E01
30
• Hot Redundancy in PACiS OI Server • 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.
Schneider Electric - CS&P – System Devices Configuration – E01
31
• Hot Redundancy in PACiS OI Server • 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): OI server failure
OI Client switching time
PC power off
Less than 20s
Application stop
Less than 20s
Ethernet disconnection
Less than 60s
Schneider Electric - CS&P – System Devices Configuration – E01
32
• Hot Redundancy in PACiS OI Server Both OI are connected on Ethernet and visible.
OI Master shuts down then restarts
Server 1
Server 2
Server 1
Server 2
START-UP
START-UP
MASTER
SLAVE
STANDALONE
WAIT
MASTER
PC halted GOING TO STANDALONE
SLAVE
STANDALONE PC start-up START-UP
SLAVE
MASTER
OI is proceeding consolidating messages before going to Standalone.
Schneider Electric - CS&P – System Devices Configuration – E01
33
• Hot Redundancy in PACiS OI Server One OI is not connected and reconnects.
One OI is not connected and reconnects. Server 1
Server 2
START-UP
START-UP
STANDALONE
STANDALONE
Server 2
Server 1 START-UP
START-UP
STANDALONE
STANDALONE
Ethernet connexion Ethernet connexion
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)
Case 1 : no OI client connected on OI server 1
SHUTDOWN SHUTDOWN
START-UP START-UP
MASTER SLAVE
SLAVE
MASTER
Schneider Electric - CS&P – System Devices Configuration – E01
34
• Hot Redundancy in PACiS OI Server Fault Tolerance automation : principle of MASTER/SLAVE election 1. 2.
The 1st server that starts is MASTER 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
Schneider Electric - CS&P – System Devices Configuration – E01
35
• Hot Redundancy in PACiS OI Server 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
Schneider Electric - CS&P – System Devices Configuration – E01
36
• Hot Redundancy in PACiS OI Server 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.
Schneider Electric - CS&P – System Devices Configuration – E01
37
• Buffered Reports for PACiS OI Server 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 : Functionality can be tested on OI event viewer (printer is depending on its own buffer) A Buffer overflow DP is reached in that case.
Schneider Electric - CS&P – System Devices Configuration – E01
38
View more...
Comments
