Pacis Sbus Agency: Sbus/En T/D10

PACiS SBUS AGENCY
SBUS/EN T/D10
Technical Guide
Technical Guide SBUS/EN T/D10
PACiS SBUS Agency Page 1/2
PACiS STATION BUS AGENCY IEC 61850

CONTENTS
Safety & Handling SBUS/EN SA/D10
Introduction SBUS/EN IT/D10
Installation SBUS/EN IN/D10
Settings SBUS/EN ST/D10
Commissioning SBUS/EN CM/D10
Applications SBUS/EN AP/D10
Functional Description SBUS/EN FT/D10
Technical Data SBUS/EN TD/D10
Maintenance SBUS/EN MF/D10
Glossary PACiS/EN LX/D10

SBUS/EN T/D10 Technical Guide
Page 2/2 PACiS SBUS Agency
BLANK PAGE
PACiS SBUS Agency
SAFETY & HANDLING

CONTENTS
1. SCOPE OF THE DOCUMENT 3
2. SAFETY 4
2.1 Health and Safety 4
2.2 Explanation of symbols and labels 4
2.3 Installing, Commissioning and Servicing 4
2.4 Decommissioning and Disposal 4
3. GUARANTEES 5
4. COPYRIGHTS & TRADEMARKS 6

4.1 Copyrights 6
4.2 Trademarks 6
5. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC

PRODUCTS 7
SBUS/EN SA/D10 Safety & Handling
BLANK PAGE
1. SCOPE OF THE DOCUMENT

The present document is a chapter of the PACiS SBUS Agency documentation. It describes
the safety, handling, packing and unpacking procedures applicable to PACiS SBUS Agency
software.
2. SAFETY
WARNING: THIS SAFETY SECTION SHOULD BE READ BEFORE COMMENCING
ANY WORK ON THE EQUIPMENT.
2.1 Health and Safety
The information in the Safety Section of the product documentation is intended to ensure
that products are properly installed and handled in order to maintain them in a safe condition.
It is assumed that everyone who will be associated with the equipment will be familiar with
the contents of the Safety Section and all Safety documents related to the PC and
Communication networks.
2.2 Explanation of symbols and labels
The meaning of symbols and labels may be used on the equipment or in the product
documentation, is given below.
2.3 Installing, Commissioning and Servicing
Equipment operating conditions
The equipment (PC and communication network supporting PACiS GATEWAYS) should be
operated within the specified electrical and environmental limits.
Fibre optic communication
Where fibre optic communication devices are fitted, these should not be viewed directly.
Optical power meters should be used to determine the operation or signal level of the device.
2.4 Decommissioning and Disposal
Disposal:
It is recommended to avoid incineration and disposal of the PC and the communication
network supporting PACiS STATIONBUS. The products should be disposed of in a safe
manner.
3. GUARANTEES
The media on which you received Schneider Electric software are guaranted not to fail
executing programing instructions, due to defects in materials and workmanship, for a period
of 90 days from date of shipment, as evidenced by receipts or other documentation.
Schneider Electric will, at its option, repair or replace software media that do net execute
programming instructions if Schneider Electric receive notice of such defects during the
guaranty period. Schneider Electric does not guaranty that the operation of the software shall
be uninterrupted or error free.
A Return Material Authorisation (RMA) number must be obtained from the factory and clearly
marked on the package before any equipment acceptance for guaranty work.
Schneider Electric will pay the shipping costs of returning to the owner parts, which are
covered by warranty.
Schneider Electric believe that the information in this document is accurate. The document
has been carefully reviewed for technical accuracy. In the event that technical or
typographical errors exist, Schneider Electric reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Schneider Electric if errors are suspected. In no event shall
Schneider Electric be liable for any damages arising out of or related to this document or the
information contained in it.
Expect as specified herein, Schneider Electric makes no guaranties, express or implied and
specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part
Schneider Electric shall be limited to the amount therefore paid by the customer.
Schneider Electric will not be liable for damages resulting from loss of data, profits, use of
products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Schneider Electric will apply regardless of the form of action,
whether in contract or tort, including negligence. Any action against Schneider Electric must
be brought within one year after the cause of action accrues. Schneider Electric shall not be
liable for any delay in performance due to causes beyond its reasonable control.
The warranty provided herein dues net cover damages, defects, malfunctions, or service
failures caused by owner's failure to follow the Schneider Electric installation, operation, or
maintenance instructions; owner's modification of the product; owner's abuse, misuse, or
negligent acts; and power failure or surges, fire, flood, accident, actions of third parties, or
other events outside reasonable control.
4. COPYRIGHTS & TRADEMARKS

4.1 Copyrights
Under the copyright laws, this publication may not be reproduced or transmitted in any form,
electronic or mechanical, including photocopying, recording, storing in an information
retrieval system, or translating, in whole or in part, without the prior written consent of
Schneider Electric.
4.2 Trademarks
PACiS, PACiS SCE, PACiS ES, PACiS SMT, PACiS PS, PACiS SCE, MiCOM are
trademarks of Schneider Electric. Product and company names mentioned herein are
trademarks or trade names of their respective companies.
5. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS

Schneider Electric products are not designed with components and testing for a level of
reliability suitable for use in or in connection with surgical implants or as critical components
in any life support systems whose failure to perform can reasonably be expected to cause
significant injuries to a human.
In any application, including the above reliability of operation of the software products can be
impaired by adverse factors, including -but not limited- to fluctuations in electrical power
supply, computer hardware malfunctions, computer operating system, software fitness,
fitness of compilers and development software used to develop an application, installation
errors, software and hardware compatibility problems, malfunctions or failures of electronic
monitoring or control devices, transient failures of electronic systems (hardware and/or
software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons
(including the risk of bodily injuries and death) should not be reliant solely upon one form of
electronic system due to the risk of system failure to avoid damage, injury or death, the user
or application designer must take reasonably steps to protect against system failure,
including -but not limited- to back-up or shut-down mechanisms, not because end-user
system is customised and differs from Schneider Electric testing platforms but also a user or
application designer may use Schneider Electric products in combination with other
products.
These actions cannot be evaluated or contemplated by Schneider Electric; Thus, the user or
application designer is ultimately responsible for verifying and validating the suitability of
Schneider Electric products whenever they are incorporated in a system or application, even
without limitation of the appropriate design, process and safety levels of such system or
application.
BLANK PAGE
PACiS SBUS Agency
INTRODUCTION
CONTENTS
1. INTRODUCTION 3
2. INTRODUCTION TO PACiS SBUS AGENCY' GUIDE 4

2.1 Chapters description 4
2.1.1 Safety (SA) Chapter 4
2.1.2 Introduction (IT) Chapter 4
2.1.3 Installation (IN) Chapter 4
2.1.4 Settings (ST) Chapter 4
2.1.5 Commissioning (CM) Chapter 4
2.1.6 Applications (AP) Chapter 4
2.1.7 Functional Description (FT) Chapter 4
2.1.8 Technical Data (TD) Chapter 4
2.1.9 Maintenance (MF) Chapter 4
2.1.10 Lexicon (LX) Chapter 4
3. INTRODUCTION TO PACiS SBUS AGENCY 5

3.1 What are PACiS Products? 5
3.2 Application and Scope of PACiS SBUS Agency 5
SBUS/EN IT/D10 Introduction
BLANK PAGE
1. INTRODUCTION
The present document is a chapter of the PACiS SBUS Agency documentation. It describes
the documentation’s chapters you can find in the different guides, the types of applications
and how to use the product. It is the Introduction (IT) chapter of this Product's manual.
2. INTRODUCTION TO PACiS SBUS AGENCY' GUIDE

This version of the PACiS SBUS documentation refers to version PACiS V4.7. The guide
provides functional and technical descriptions of the product and of a comprehensive set of
functions for the product’s use and applications.
PACiS SBUS Agency Technical Guide: contains information on the installation and
commissioning of the product, and also a fault finding section. This volume is intended for
site engineers who are responsible for the installation, commissioning and maintenance of
the product.
2.1 Chapters description
2.1.1 Safety (SA) Chapter
This chapter contains the safety instructions, handling and reception of electronic equipment,
packing and unpacking of parts, Copyrights and Trademarks.
2.1.2 Introduction (IT) Chapter
This is the present document, it contains the description of each chapter of the PACiS SBUS
Agency guides
2.1.3 Installation (IN) Chapter
This chapter contains the installation procedures.
2.1.4 Settings (ST) Chapter
This chapter contains the list of the setting with defaults values and range of the PACiS
SBUS Agency.
2.1.5 Commissioning (CM) Chapter
This chapter contains instructions on how to commission PACiS SBUS Agency, comprising
checks on the settings and functionalities.
2.1.6 Applications (AP) Chapter
This chapter describes how to use the PACiS SBUS Agency with Equipment Simulator.
2.1.7 Functional Description (FT) Chapter
This chapter contains a description of the product. It describes the functions of the PACiS
SBUS Agency.
2.1.8 Technical Data (TD) Chapter
This chapter contains the technical data including, accuracy limits, recommended operating
conditions, ratings and performance data.
It also describes environment specification, compliance with technical standards.
2.1.9 Maintenance (MF) Chapter
This chapter contains information for advanced maintenance operations. It is meant for
experts.
2.1.10 Lexicon (LX) Chapter
This chapter contains lexical description of acronyms and definitions.
3. INTRODUCTION TO PACiS SBUS AGENCY

Schneider Electric philosophy is to provide a full range of products, computers, gateways
and IEDs products. Each of these products can be used independently, or can be integrated
to form a PACiS system: a Digital Control System (DCS) SCADA system.
3.1 What are PACiS Products?
Driven by worldwide requirements for advanced applications in SCADA, Digital Control
Systems, Automation, control and monitoring, Schneider Electric have designed and
developed a new and comprehensive system: PACiS, specifically intended for the power
process environment and electrical utility industry. It allows building of a customised solution
for Control, Monitoring, Measurement and Automation of electrical processes.
This new generation of products has been specially tailored for the PACiS system. A major
objective for PACiS products is to make this range as easy as possible for the customer to
accept, adapt and integrate into their system and operation.
One of the key features is that this product family is based on an IEC61850 client/server
architecture.
3.2 Application and Scope of PACiS SBUS Agency
PACiS DCS solution is based on a Station Bus over Ethernet TCP/IP IEC61850. Each piece
of equipment directly connected on the PACiS SBUS uses this agency to exchange data in
order to perform all required function of the application.
The PACiS SBUS Agency is compatible with Microsoft Windows™ Seven Pro 32 Bits SP1,
Windows 2003 Server, Windows™ XP, Windows™ XP embedded and VxWorks OS
(Operating System).
BLANK PAGE
PACiS SBUS Agency
INSTALLATION
CONTENTS
2. GENERAL DESCRIPTION 4
2.1 PACiS SBUS Agency installation 4
SBUS/EN IN/D10 Installation
BLANK PAGE

This document is a chapter of the PACiS documentation. It describes the installation
procedure of the SBUS Agency.
The objective of this document is to install all needed to run the PACiS SBUS Agency.
2. GENERAL DESCRIPTION
The communication between PACiS equipment on the Station Bus is based on the SBUS
agency.
The agency must be installed on each PC which embeds the PACiS SUI, the PACiS SMT,
the PACiS GTW and the PACiS ES.
On the PACiS GTW PC, the PACiS GTW Installer installs an agency release: refer to your
PACiS System Release
Note 1: to check if this PACiS SBUS agency release is the good one. If no, you have to
uninstall this release and install a new one.
Note 2: before updating the SUI agency, stop the Pacis SUI service.
2.1 PACiS SBUS Agency installation
This section describes the procedure for a complete Installation or reinstallation for PACiS
AGENCY.
Before beginning the PACiS SBUS installation, Windows Seven must be configured,
do following:
Step Action
1 Administrator rights
The Installation on Windows Seven must be done with Administrator rights.
Check/Configure the user account type:
• Access "Control Panel > User Accounts safety > User account"
• Click "Change your account type"
• Choose/check option "Administrator"
• Click "Change Account type"
Step Action
2 Disabling Windows Update
The Windows Update from the Control Panel is to be inactive.
• Access "Control Panel > System and Security > Windows Update"
• Click "Turn Windows Update on or off"
• Choose option "Never check for updates"
• Click "OK"
To install PACiS SBUS, do following:
Step Action
1 Double-click the Agency_x.y.exe to install PACiS SBUS application (x.y is the PACiS
SBUS release number).
• Choose the Language

• Click OK in the Wizard
2
• Click Next in the Wizard.

Step Action
3
• Read the License Agreement, select I accept the agreement

• Click Next in the Wizard.
4
• In the "Select Destination Location" dialog box define the installation folder (the
default installation folder is C:\Program Files\PACIS\SBUS)
• Click Next
Step Action
5
• In the "Select Components" dialog box define the Operating System (the default
installation folder is Windows Seven / Windows XP)
• Click Next
6 • In the "Select Start Menu Folder" window, select the shortcut Location to launch the
Agency (in PACiS folder by default)
• Click Next.
7
• Select if first install or not (First installation by default)

• Click Next.
Step Action
8
• Check that the proposed settings are the correct ones

• Click Install.
9 In the "Installing" dialog box displays the Installation progress
Step Action
10 The "WinPcap Installer" dialog box is proposed during the Installation
• Click Next
• And follow instructions
11
The installation of WinPcap is now complete.

• Click Finish
Step Action
12
The installation of AGENCY is now complete.

• Click Finish
NOTE 1: The agency must be installed on each PC which supports the

PACiS SUI / OI, the SMT, the Equipment Simulator, and the
Gateway.
NOTE 2: During installation, Dr Watson is enabled and configured with
specific parameters; if others applications are installed after
SBUS Agency and alter the Dr Watson parameters, the exception
handling may have an unexpected behavior. So it is advised to
check before running SBUS Agency that the following registry
parameters are these ones.
PACiS SBUS Agency
SETTINGS
CONTENTS
2. CONFIGURATION FILES 4
2.1 Agency configuration file 4
2.1.1 Explanation of configuration parameters 4
2.1.2 Example of “Agency.cfg” file 5
2.2 Network configuration file 6
2.2.1 Explanation of network configuration parameters 6
2.2.2 Example of “ Lean.cfg ” file 8
2.3 Log configuration file 10
2.3.1 Explanation of log configuration parameters 10
2.3.2 Example of “mms_log.cfg” file 10
SBUS/EN ST/D10 Settings
BLANK PAGE

This document is a chapter of the PACiS Station BUS Agency documentation. It describes
the Settings which can modify the behaviour of this product.
The setting is done through modifying configuration files..
This chapter defines settings with default value setting at the installation time. But also
shows which settings to modify for obtaining typical use case of the application.
2. CONFIGURATION FILES
These components are delivered with agency as a sample, they have to be customised by
the user or in the final stage to be generated by the SCE. The structure of these files shall
not be changed by the user except the comment prefixed by a # character.
A good practice is before editing the file to make a copy to keep default parameters and
settings.
Before the SBUS Agency can run there are configuration files that must be present in the
directory of the agency’s executable.
Here is the list of the configuration files and there explanations:
Agency.cfg Agency configuration file. This file defines some vital

parameters for the agency in terms of size and
numbers of objects.
Lean.cfg Network configuration file. This file contains 2 kinds
of parameters:
• SISCO stack low layers parameters (for MMS,
CLNP, TP0, TP4 …)
• Network addressing (name and IP addresses of
server applications)
mms_log.cfg Log configuration file. This file is used to customize
(name, size, enable/disable) logs performed by
SISCO stack and the agency.
More details in SISCO documentation.
See the following chapter for details about the contents of these files.
2.1 Agency configuration file
Most parameters are optional unless stated that they are mandatory. If an optional
parameter is not configured in this file a default value will be used.
2.1.1 Explanation of configuration parameters
Here is the list of the parameters you will find in the “Agency.cfg” file with their description
and their default values:
Parameter name Description / role Default Min Max value

value value
Life_Timeout Is a LONG decimal integer to set the Life 5000 2000 30000
Timeout delay (in ms) between two
consecutives Life Messages.
Max_Slow_Link_Signals Is a SHORT decimal integer to set the 8 2 12
maximum number of OnSlowLink()
consecutive calls before an association has
to be closed.
MaxClientSession Is the maximum number of client sessions 3 for Win 0 10
managed by the agency.
1 for VxW
MaxServerSession Is the maximum number of server sessions 1 0 50
managed by the agency.
MaxServersPerClient Is the maximum number of server 50 1 96
applications that a client session will
associate with.
MaxDomainsPerServer Is the maximum number of domains (or 2 1 50
logical devices) defined in a data model
server.
Parameter name Description / role Default Min Max value

value value
MaxReqCalling Is the maximum number of pending requests 50 10 100
received by the agency.
MaxReqCalled Is the maximum number of pending requests 50 10 100
sent by the agency.
MaxClientAssoc Is the maximum number of client 5 1 20
associations for a server session.
ClockSynchroPeriod Is the station bus master clock 60 10 3600
synchronisation period (unit = second).
DoubleStandbyFilter Is the timeout for filtering the redundancy 40000 5000 60000
Timeout switch when the 2 servers are “standby”. If
this timeout elapses, data are reported to
UNKNOWN by agency (unit=ms)
sntpServer1 Is the IP address of first SNTP server - - -
sntpServer2 Is the IP address of second SNTP server - - -
The second SNTP server is optional and
defined for clock synchro redundancy
purpose.
2.1.2 Example of “Agency.cfg” file

Following an example of the “Agency.cfg” file:
#---------------------------------
# Agency specific parameters
#---------------------------------
%SpeParms_Begin
Life_Timeout = 5000
Max_Slow_Link_Signals = 2
MaxClientSession = 1
MaxServerSession = 1
MaxServersPerClient = 1
MaxDomainsPerServer = 10
MaxReqCalling = 50
MaxReqCalled = 50
MaxClientAssoc = 5
ClockSynchroPeriod = 60
DoubleStandbyFilterTimeout = 5000
sntpServer1 = 10.22.92.189
%SpeParms_End
2.2 Network configuration file

Most parameters are optional unless stated that they are mandatory. If an optional
parameter is not configured in this file a default value will be used.
This file describes for the whole agency (i.e. for all the open sessions):
• SISCO stack low layers parameters (for MMS, CLNP, TP0, TP4…)
• the network addressing parameters (alias name, IP address, AP title, AE qualifier per
server application)
2.2.1 Explanation of network configuration parameters
Here is the list of the parameters you will find in the “Lean.cfg” file with there description and
there default values:
Parameter name Description / role Default value

CLNP parameters These parameters concern the connection less protocol
mode. They will be detailed once GOOSE messages are
Lifetime
implemented in the agency.
Lifetime_Decrement
Cfg_Timer
Esh_Delayent
Local_MAC
Local_NSAP
(embraced by
%Clnp_Begin and
%Clnp_End)
TP4 parameters As we are using MMS over TCP RFC1006, only the 2
following parameters are significant
(embraced by
%Tp4_Begin and
%Tp4_End)
rfc1006_Max_Tpdu_ Is the maximum length of a TPDU 8192
Len
rfc1006_Max_Num_ Is the maximum number of connections. (MaxClientSession *
Conns MaxServersPerClient
This value shall be consistent with some parameters of
+ MaxServerSession *
Agency.cfg according to this equation:
MaxClientAssoc)
rfc1006_Max_Num_Conns >= (MaxClientSession *
MaxServersPerClient + MaxServerSession *
MaxClientAssoc)
Local server These parameters shall be left as they are. As defined below in
parameters appendix C.
(embraced by
Begin_Local and
End_Local)
Parameter name Description / role Default value

Remote server These parameters define the IEC61850 network
parameters “signature” of one server.
(embraced by There are as many Begin_Remote / End_Remote blocks
Begin_Remote and as the number of remote server that the agency wants to
End_Remote) connect. This list may be an overset of the remote
servers that the agency wants to connect, including
remote servers not connected by the agency.
Note : lean.cfg may be unique for the SCS if it contains
the exhaustive list of IEC61850 applications configured.
Common_Name Is the alias name in the scope of the IEC61850 network <application name>
(station bus).
One Common_Name shall be associated to one unique
parameter set {IP_addr, AP_Title, AE_Qualifier}.
Common_Name shall be the same than its associated
data model base name (without .dm suffix).
Common_Name is case sensitive and shall be less than
8 characters due to VxWorks file system limitaion.
AP_Title MMS parameter. Always set at the default value. 1 3 9999 23
AE_Qualifier Is the extension of the IP address if several server 1
applications are using a same agency.
It shall start at 1 for the first application, then 2 for the
second and so on… until 50 maximum.
Psel MMS parameter. Always set at the default value. 00 00 00 01
Ssel MMS parameter. Always set at the default value. 00 01
Tsel MMS parameter. Always set at the default value. 00 01
Transport Defines the transport layer used. The only mode allowed TCP
is TCP, so always set at the default value.
NSAP These parameters concern the connection less protocol 49 00 01 53 49 53 43
mode. It will be detailed once GOOSE messages are 09 01 01
implemented in the agency.
For now, always set at the default value.
Ip_addr Is the IP address of the application host device.
Format : a.b.c.d
2.2.2 Example of “ Lean.cfg ” file

Following an example of the Lean.cfg file:
#---------------------------------
# CLNP specific parameters
#---------------------------------
%Clnp_Begin
# TP4 only CLNP parameters:
# -------------------------
Lifetime = 50 # TPDU lifetime (in 500 ms units)
Lifetime_Decrement = 1 # TPDU lifetime decrement (in 500msec units)
Cfg_Timer = 120 # Configuration Timer in seconds
Esh_Delay = 5 # Delay time before first ESH sent (in seconds)
Local_MAC = 00 20 # Local MAC address (up to 6 hex bytes)
Local_NSAP = 49 00 01 53 49 53 43 09 00 01 # Local NSAP (up to 20 hex bytes)
%Clnp_End
#---------------------------------
# TP4 or TCP specific parameters
#---------------------------------
%Tp4_Begin
# TP4 only parameters:
# --------------------
Max_Tpdu_Length = 128 # Max length of TPDU.
Max_Remote_Cdt = 4 # Max credits we can handle.
Local_Cdt = 4 # CDT value we will ALWAYS send in ACK.
Max_Num_Connections = 10 # Max number of connections.
Max_Spdu_Outstanding = 4 # Max num of SPDUs outstanding per connextion.
Window_Time = 10 # Window Time (in seconds).
Inactivity_Time = 120 # Inactivity Time (in seconds).
Retransmission_Time = 10# Retransmission Time (in seconds).
Max_Transmissions = 2 # Max number transmissions of a TPDU.
Ak_delay = 2
# TCP (RFC1006) only parameters:

# ------------------------------
rfc1006_Max_Tpdu_Len = 8192 # Max length of TPDU.
rfc1006_Max_Num_Conns = 400 # Max number of connections.
%Tp4_End
#---------------------------------
# DIB specific parametrs
#---------------------------------
%Dib_Begin
Begin_Local
Common_Name = local1
AP_Title = 1 3 9999 33
AE_Qualifier = 33
Psel = 00 00 00 01
Ssel = 00 01
Tsel = 00 01
Transport = TCP # TP4 or TCP or TPX
# Transport = TP4 # TP4 or TCP or TPX
# Transport = TPX # TP4 or TCP or TPX
End_Local
Begin_Remote
Common_Name = remote1
AP_Title = 1 3 9999 23
AE_Qualifier =1
Psel = 00 00 00 01
Ssel = 00 01
Tsel = 00 01
Transport = TCP
# Transport = TP4
# Transport = TPX
NSAP = 49 00 01 53 49 53 43 09 01 01
Ip_addr = 180.9.114.245
End_Remote
Begin_Remote
Common_Name = remote2
AP_Title = 1 3 9999 23
AE_Qualifier = 2
Psel = 00 00 00 01
Ssel = 00 01
Tsel = 00 01
Transport = TCP
NSAP = 49 00 01 53 49 53 43 09 01 01
# Ip_addr = 180.9.117.164
Ip_addr = 180.9.114.245
End_Remote
%Dib_End
2.3 Log configuration file
2.3.1 Explanation of log configuration parameters
Parameter name Description/role Default value

FileLogEn If not commented (prefix by #), log is activated Enabled
LogFileSize Maximum log file size, logged lines are wrapped 2000000
once size is reached
LogFileName Name of the log file Agency.log
Other parameter Cf mms_log.cfg directly or SISCO documentation -
2.3.2 Example of “mms_log.cfg” file

Following an example of the “mms_log.cfg” file:
####################################################################
#
# COMPONENT_NAME: MMS-EASE Lite Logging Configuration File
#
# mms_log.cfg
#
# This file is used to set the log masks used to control l
# logging performed by the MMS-EASE Lite Debug Libraries, as well as
# to set memory debug flags. This module is read by the source
# module 'log_cfg.c'.
#
####################################################################
%LogBegin
############# GENERAL LOG CONTROL ############

# ------- Log File Attributes
FileLogEn # Log to a file
LogFileSize= 2000000
LogFileName= agency.log
# ------- Memory Resident Logging Attributes

# MemLogEn # Log to memory
# LogMemItems= 1000
# DumpFileName= mmsdmem.log
# MemAutoDump
# ------- Misc. Control Flags

TimeEnable= 2 # 1 = Time/date, 2 = Elapsed time
NoAppend # means destroy existing file
# Setbuf # use setbuf(fh,NULL) after open
# NoMsgheader # don't print message identifier
# NoWipe # don't wipe bar in wrapped file
# NoWrap # don't wrap the file
# HardFlush # close and reopen the file each time
# NoHeaderCr # No CR after header line
# SuppressFilename # No file/line
# SuppressLogtype" # No log type
############# LOG MASKS ############

#
# ------ ASN.1 logging
# ASN1_LOG_NERR # Recoverable ASN.1 errors ( bad grammar )
# ASN1_LOG_DEC # Parses class, form, tag, length, and contents
# ASN1_LOG_ENC # Shows encoding of a PDU at the ASN.1 level
#
# ------ MMS logging
MMS_LOG_NERR # Recoverable MMS errors ( bad grammar )
# MMS_LOG_DEC # Shows states used in the parse of an MMS PDU
# MMS_LOG_ENC # Shows encoding of an MMS PDU
MMS_LOG_RT # Logs creation of Runtime types
# MMS_LOG_RTAA # Logs creation of Runtime types using
AlternateAccess
# MMS_LOG_AA # Logs creation of AlternateAccess
#
# ------ MVL logging
MVLLOG_NERR #
MVLLOG_ACSE #
# MVLLOG_ACSEDATA #
# MVLULOG_FLOW #
#
# ------ ACSE logging
# ACSE_LOG_ENC #
# ACSE_LOG_DEC #
#
# ------ Transport (TP4/TCP) logging
# TP4_LOG_FLOWUP # Log TP4/TCP indications
# TP4_LOG_FLOWDOWN # Log TP4/TCP requests
#
# ------ CLNP logging

CLNP_LOG_NERR # log normal errors (recoverable errors)
# CLNP_LOG_REQ # log NS-USER requests, or write to socket
# CLNP_LOG_IND # log NS-USER indications, or read from socket
#
# CLNP_LOG_ENC_DEC # log CLNP encoding/decoding of NPDUs
# CLNP_LOG_LLC_ENC_DEC # log LLC encoding/decoding
# CLSNS_LOG_REQ # log SN-USER requests (sub-network)
# CLSNS_LOG_IND # log SN-USER indications (sub-network)
#
# ------ ADLC logging
# ADLC_LOG_NERR #
# ADLC_LOG_FLOW #
# ADLC_LOG_IO #
# ADLC_LOG_HEXIO #
# ADLC_LOG_SM # Serial manager
# ADLC_LOG_HEXSM # Serial manager data
# ADLC_LOG_USER # User
# ADLC_LOG_HEXUSER # User data
#
# ------ SMP logging
SMP_LOG_REQ #
SMP_LOG_IND #
# ------ MEMORY Allocation logging

# MEM_LOG_CALLOC # Calloc logging
# MEM_LOG_MALLOC # Malloc logging
# MEM_LOG_REALLOC # Realloc logging
# MEM_LOG_FREE # Free logging
#
# Memory Allocation Debug Control
# m_fill_en
# m_heap_check_enable
# m_check_list_enable
# m_find_node_enable
# m_track_prev_free
# list_debug_sel
# m_no_realloc_smaller
%LogEnd
PACiS SBUS Agency
COMMISSIONING
CONTENT

1.1 Introduction 3
1.2 Requirements 3
2. CHECKING SOFTWARE INSTALLATION 4

SBUS/EN CM/D10 Commissioning
BLANK PAGE

This document is a chapter of the PACiS documentation. It describes the commissioning of
the SBUS Agency product. This chapter follows the SBUS/EN IN (Installation) chapter.
1.1 Introduction
The PACiS SBUS Agency application will run on a Windows Seven Pro 32 Bits SP1or
Windows 2003 Server or Windows XP and Windows XP embedded OS (Operating System).
So commissioning consists of looking at the start-up of this PC; checking for the application
to be correctly installed.
1.2 Requirements
It is essential that all requirements expressed in SBUS/EN IN (Installation) chapter has been
fulfilled.
2. CHECKING SOFTWARE INSTALLATION

As this product is a software application running on a PC, commissioning will consist of
looking at the following files to be installed. For more details about the behaviour of this
application see the chapter Application (SBUS/EN AP) of this product. If there are troubles
about the behaviour of this application, see the chapter Maintenance (SBUS/EN MF) of this
product.
If the installation of PACiS SBUS Agency is under the directory named “C:\Program
Files\PACiS”, the following directory-tree after the setup procedure is following:
In case of problems with the execution of the application depending on the messages, get in
the main application window check the existence of the above file.
C:\Program Files\PACiS
<DIR> Tunneling
<DIR> 61850Agency
C:\Program Files\PACiS\Tunneling
install_onrpc.bat
inst_pm.exe
LaunchS1V2Patu.exe Tools enabling to test the MiCOM S1 V2 functioning with

tunneling.
oncrpc.dll DLL managing ONCRPC communication [used by
PatuClient.dll, Portmap.exe, Rpcinfo.exe]
PATDbWin.exe Patu debug trace window.
PatuClient.dll Main executable of PatuClient. This DLL allows an
application software to use PACIS Tunneling.
PatuEvt.dll Contain resources used by the Windows Event log to
display text of events logged by PATU.
portmap.exe Portmap is a Windows services which enable ONCRPC
portmap.srg communication with another computer thru TCP/IP.
rpcinfo.exe Enable to look for OncRpc programs on RPC server

S1V2ModbusPatu.dll DLL to be used by MiCOM S1 V2 Modbus in order to use
PACiS Tunneling.
S1V2T103Patu.dll DLL to be used by MiCOM S1 V2 T103 in order to use
PACiS Tunneling.
S1V2_Patu.dll
SimPatuServer.exe
TsPatuClient.exe
Tunneling.reg
<DIR> src
C:\Program Files\PACiS\Tunneling\src
Header files to include into the client application and Source code files to compile and link
with the client application.
PatuClient.h
PatuClientManagement.cpp Provides an interface to manage the PatuClient.dll
PatuClientManagement.h
PatuError.cpp
PatuError.h
PatuEvt.h
PatuIO.cpp
PatuIO.h
C:\Program Files\PACiS\61850Agency
<DIR> exe
<DIR> odfoundry
<DIR> odTime
<DIR> wpdpack
<DIR> api
C:\Program Files\PACiS\61850Agency\exe
Agency.cfg Agency configuration file. This file defines some vital parameters for
the agency in terms of size and numbers of objects.
DBPacis.exe External process which prints on line the internal printf outputs of
the agency (debug traces)
Lean.cfg Network configuration file. This file contains 2 kinds of parameters:
• SISCO stack low layers parameters (for MMS, CLNP, TP0,
TP4…)
• Network addressing (names and IP addresses of server
applications)
Mms_log.cfg Log configuration file. This file is used to customize (name, size,
enable/disable) logs performed by the SISCO stack and the agency.
OdRpc.dll DLL to load dynamically with the client and/or server application.
This library manages the IPC mechanisms (Remote Procedure
Calls).
Win32Agency.exe Windows agency launcher. This will insert an icon in the icon
system tray. By right clicking on the icon, a menu is displayed. From
a window, open the agency log file, get the agency version, display
the agency trace window.
Dbwin.bat Command file to launch DBPacis.exe
OdAgency.dll
OdAgency.map
Win32Agency.map
C:\Program Files\PACiS\61850Agency\odfoundry
ALIGN.CFG Alignment configuration file for OdFoundry. This file is read by
OdFoundry to compute the right alignments (platform dependant)
exefoundry.bat
foundry.log
odfoundry.exe Schneider Electric PACiS foundry application. This tool generates
.dm files from .odf input files.
C:\Program Files\PACiS\61850Agency\api\include
basictypes.h Header files to include into the client/server application defining
GLBTYPES.H primitive types and structured types.
OdDllImport.c Utility source and header file to include into the client/server
OdDllImport.h application providing a method (OdLoadDll()) to load the library and
activate the RPC mechanism.
OdDllTypes.h Header file to include into the client/server application defining the
OdInclude.h ODST_ and ODCT_ types.
C:\Program Files\PACiS\61850Agency\OdTime
instsrv
OdTimesrv
srvany
C:\Program Files\PACiS\61850Agency\WpdPack
WinPcap_4_1_2 WinPcap Installer
In event of problems with the execution of the application depending on the messages you
get in the main application window check the existence of the above file.
Application SBUS/EN AP/D10
PACiS SBUS Agency
APPLICATION
CONTENTS
2. REQUIREMENTS 4
3. LAUNCHING THE APPLICATION 5
4. APPLICATION MENU WITH EQUIPMENT SIMULATOR 6

4.1 Item Open 6
4.2 Item Edit Flags 7
4.3 Item About Agency 7
4.4 Item Stop Agency 7
4.5 Main Window application menu 8
SBUS/EN AP/D10 Application
BLANK PAGE

The present document is a chapter of PACiS SBUS Agency documentation. It describes the
use cases of this product. This document is the Application chapter (SBUS/EN AP).
2. REQUIREMENTS
First, if it is not already done, you will need to install the PACiS Station BUS Agency, see the
chapter Installation (SBUS/EN IN) of this product.
The 4 platforms on which the agency runs are:
• Microsoft Windows™ Seven Professional 32 Bits SP1
• Microsoft Windows™ 2003 Server
• Microsoft Windows™ XP
• Microsoft Windows™ XP Embedded

3. LAUNCHING THE APPLICATION

NOTE: This part is only applicable to Microsoft Windows™ Seven Pro 32 Bits,
2003 Server, XP and XP Embedded platform.
Launch the application directly by double-clicking on the executable found at the following
place in the Windows explorer:
C:\Program Files\PACiS
FIGURE 1: LAUNCHING THE APPLICATION

But in most cases the SBUS Agency is launched by the application who needs it to
communicate on the Station BUS: PACiS GTW, PACiS SMT, PACiS ES, PACiS OI.
This is the raison why you will not find short cuts in the “Start-up” menu that it is not needed.
Once you have clicked on this executable an icon appear in the system tray and looks like
the following But in most cases the SBUS Agency is launched by the application who needs
it to communicate on the Station BUS: PACiS GTW, PACiS SMT, PACiS OI, PACiS ES.
The reason why shortcuts are not found in the “Start-up” menu is that it is not needed.
Once clicked on this executable, an icon appears in the system tray and looks like the
following:
SBUS Agency application Icon
S0428ENa
FIGURE 2: SBUS AGENCY ICON

The contextual menu can be used only with ES.
4. APPLICATION MENU WITH EQUIPMENT SIMULATOR

CAUTION: RISK OF MALFUNCTION
WE DO NOT SUPPORT THE PACIS ES. IT IS NOT COMPATIBLE WITH
PACIS V 4.7. THERE IS NO WARRANTY TO MAKE SURE THAT THE
SCENARIO GENERATOR OPERATES. YOU CAN INSTALL AND USE
THE PACIS ES ONLY AT YOUR OWN RISK.
You can install the PACiS ES on any PC (whatever its IP address), but we recommend that
you operate the PACiS ES on a separate maintenance PC, NOT on the PACiS OI or GTW
and NOT on site.
By right clicking on the application icon on the system tray, you will get the following popup
menu:
FIGURE 3: RIGHT CLICK MENU

4.1 Item Open
By double clicking on the icon of the SBUS Agency application you will get the same result
displaying the main application window as the following:
FIGURE 4: OPEN ITEM IN APPLICATION MENU

This is the content of the following file (if the agency is installed in the default
folder):
C:\Program Files\PACiS 61850Agency\exe\agency.log
4.2 Item Edit Flags

This item will let you configure the traces you want.
FIGURE 5: EDIT FLAG ITEM IN MENU APPLICATION

You can then choice the type of information logged in the agency.log file displaying in the
main application window. For an explanation of the Dialog box contents, see the chapter
Settings (SBUS/EN ST) of this product.
The level of traces must only be modified by an expert.
4.3 Item About Agency
Schneider Electric, 2008, All Rights Reserved
FIGURE 6: ABOUT DIALOG BOX

In this “SBUS about”, the following parameters are there the name of the product, the
versions number and copyright.
4.4 Item Stop Agency
FIGURE 7: STOP AGENCY DIALOG BOX

Just click on the “OK” button to stop the SBUS Agency application
4.5 Main Window application menu

Thanks to the main application window you will have access to the following menus:
In the “File” menu you will find one item to close the main window.
In the “Edit” menu you will find one item allowing you to search for a string in the log file.
In the “View” menu you will find tree item:
• Log file: to open and display the log file
• Clear Log Window: to clear the content of the main window displaying log file
• Trace Window: <not used>

In the “?” menu you will find one item to display the “About” dialog box.
PACiS SBUS Agency
FUNCTIONAL DESCRIPTION
CONTENT
2. PACiS SBUS AGENCY ARCHITECTURE 4

2.1 Definitions 4
3. SERVER APPLICATION 6
3.1 Server agency 6
3.2 Client agency 6
3.2.1 Redundancy Management 6
4. CLIENT APPLICATION 7
5. ARCHITECTURE, IMPLEMENTATION 8
5.1 Generic SBUS server agency architecture 9
5.2 Generic computer architecture 10
5.3 Operator Station architectures 12
5.3.1 Standard architecture 12
5.3.2 Integrated architecture 13
SBUS/EN FT/D10 Functional Description
BLANK PAGE

This document is a chapter of the PACiS SBUS Agency documentation. It is the functional
description of PACiS Station Bus Agency dedicated to the communication over Ethernet of
the PACiS system and sub-systems
2. PACiS SBUS AGENCY ARCHITECTURE
2.1 Definitions
A PACiS system can be summarised as follows:
Device Device
Device Device
IED IED IED IED
Station Bus
Legacy Bus (Modbus ; 60870-5-103, ... )
S0419ENb
Device on Legacy Bus are interfaced by Gateway Device. They are not concerned by
System ‘mechanisms’. In the following sections only the device connected on the Station
Bus are considered.
2 kinds of device connected to Station Bus can be differentiated:
• PACiS device: a device implementing an SBUS server respecting the PACiS

specifications (i.e. C264, HMI, TI, BI) in terms of rules and guidelines for data
modelling. In this document all the behaviours described relating to SBUS server
• non PACiS device: a device implementing an SBUS server independently of the

PACiS rules and guidelines (Schneider Electric Px4x, Px3x, ABB, GE, SIEMENS
protections…)
It exists only 1 station bus within 1 PACiS system.
A device communicating on the station bus is typically as follows:
A p p lic a tio n
SBU S API
S B U S in te rfa ce
m o d u le
U C A 2 / IEC 6 1 8 5 0
L a ye r
MMS
… S B U S A g e n cy
TC P
IP
E th e rn e t
D e vice
S 0420E N b
Application stands for HMI, System Management Tool, Computer application (including
Telecontrol Interface), protective relay and MiCOM S1. Each one corresponds to an SBUS
server (defined by an IP @ and a specific AE qualifier).
Several applications may run on a same device and thus connect to a common SBUS
agency.
Application i
Application j
SBUS Agency Device #n
SBUS Agency SBUS Agency
Application z
Application k Application l
Device #p Device #m
S0421ENa
The SBUS agency is a unique software module which offers SBUS Client and SBUS Server
services, meaning that an Application can act as a Client and/or Server.
4 functional modules are distinguished in the following §, they are:
• Client SBUS agency
• Server SBUS agency
• Client application
• Server application
Client and server applications may be separate software modules or merged in one.
3. SERVER APPLICATION
This is an application composed with one or more tasks managing:
• any local function (I/O acquisition, filtering, processing …)
• a real time database containing the current status and attributes of server data objects
• a configuration database containing the static description of the server data objects
with their identifiers
• a non volatile memory for storing logs of time tagged events
• detection of events (data value/quality/time changes )
3.1 Server agency

• the server SBUS stack based on MMS, TCP/IP (or PPP if not on Ethernet)
• the connections with client agencies (open, shutdown, life messages)
• the associations between client and server applications
• the SBUS data object modeling structures (bricks and class) and data object
identifiers
• reports transmission according to events detected by server applications
• logs transmission
The server agency is accessible through a programmatic interface (API), allowing to open
sessions with one or more server applications.
3.2 Client agency

• the client SBUS stack based on MMS, TCP/IP (or PPP if not on Ethernet)
• the connections with server agencies (open, shutdown, life messages)
• the associations between client and server applications

The client agency is accessible through a programmatic interface (API), allowing to open
sessions with one or more client applications.
3.2.1 Redundancy Management
During the switchover time of redundant IEC61850 servers, in order to secure the dataflow
applied on SBUS data reception is filtered by IEC61850 client Agency with specific
redundancy Algorithm.
In case of failure of one redundant server, data are immediately transmitted to upper level
and implies:
• No loss of data for archiving purpose,
• Data refresh ensuring no discrepancy between switchyard real status and TBUS DCS
status list during switchover time.
4. CLIENT APPLICATION
• any system function
• a configuration database containing the list of servers to connect and the associated
data objects with their identifiers to read or to control
NOTES: - Normally SBUS allows for a client to read the data object modelling
in the server once an Association has been initialized. We do not
intend to use this feature but client is configured through its
ApplicationDatabag.
- It shall possible to communicate remotely to Schneider Electric
computers through SBUS over PPP connecting a modem on a
serial port.
5. ARCHITECTURE, IMPLEMENTATION
The API described hereafter is split into 3 parts:
• One concerning the common services used by client and server application
• One concerning client side between client agency and client application
• One concerning server between server agency and server application

The general architecture is the following:
The applications communicate to the SBUS agency via its Services DLL. The DLL to SBUS
agency interface is by some IPC mechanism handled by the Agency.
Each Application passes the services DLL a reference to a table of function pointers on
initialisation (using OpenSession() service) that it uses to implement the API callback
interface.
When the Agency needs to invoke a callback function in an application, it transfers the
request over the same IPC mechanism to its Services DLL. This DLL selects the appropriate
Application function pointer table and calls the appropriate function to implement the callback
API.
A difference exists between Microsoft Windows 2003 Server, XP, XP embedded and
VxWorks concerning the IPC implementation but this does not affect the Application source
codes.
5.1 Generic SBUS server agency architecture
Application #n
UCA2 agency
server part Application #1
Server configuration Acquisition,

config services
S Administration
Config DB filtering,
processing
B
U
S Manages data access Real time
data services Data access
network
st Read, write DB
exchanges a Supervision,
c Control,
Time synchro
k Manages reports
report services Compute event
- Send reports
Get changes of status
SI Send Goose
Receive Goose
S Goose services
C Data logger
O ApplicationDataB
Non volatile log ag ,
(circular queue) Disturbance
File transfers records
file services
S0423ENa
5.2 Generic computer architecture
Station bus
Computer
SBUS Communication Agency
Client & server services
Application
Telecontrol interface modules Databag
Computer application
Real time
DB.
Legacy protocol modules I/O processing module
IED #i
IED #j
Digital/Analog I/Os
IED #k
S0424ENa
In this architecture, there is 1 application which is server of data objects coming from local
I/O processing and coming from IEDs connected to legacy bus(es). The controller
application acts as an IED concentrator.
There is a single application databag for this device which shall contain all the necessary
parameters:
• for physical I/O processing
• for IED communications
• for SBUS agency configuration

Depending on the functions performed by the modular computer, its application may also be
an SBUS client. Typically if managing system wide interlocking or voltage regulation.
Example: Application to Bus Interface architecture
Station bus
Bus Interface device
SBUS Communication Agency
Computer
application
Application
Real time Databag
DB.
Legacy protocol modules
IED #i
IED #j
IED #k
S0425ENa
In this architecture, there is 1 application which is server of data objects coming from IEDs
connected to legacy bus(es).
Depending on the functions performed by the IED connected, Application may also be a
SBUS client.
5.3 Operator Station architectures

5.3.1 Standard architecture
Station bus
Operator
Station
SBUS Agency (EXE)
HMI application SMT application

(SCADA2000)
Real time Application

DB. Databag System
Application
Databag
HMI processing modules :

synoptics, alarms, logs…
S0426ENb
5.3.2 Integrated architecture
In this case, each Application is supported by a separate processor and has its own Ethernet
port.
BLANK PAGE
PACiS SBUS Agency
TECHNICAL DATA
CONTENTS
2. HARDWARE & SOFTWARE REQUIREMENTS 4

2.1 PACiS OI Server / SUI 4
2.2 PACiS SMT Kernel 4
2.3 PACiS SMT Kernel (MiCOM A300) 4
2.4 PACiS GTW 4
2.5 PACiS GTW (MiCOM A300) 4
2.6 PACiS ES 4
SBUS/EN TD/D10 Technical Data
BLANK PAGE

This document is a chapter of PACiS SBUS Agency documentation, describing the
Technical data of this software application.
SBUS/EN TD/D10 Technical Data
2. HARDWARE & SOFTWARE REQUIREMENTS

The following tables give the minimum hardware & software requirements to run correctly
PACiS SBUS Agency applications on PC supporting PACiS software.
2.1 PACiS OI Server / SUI
RAM 2048 Mbytes or more

Hard disk 120 Gbytes or more
CPU Core II duo 2.66 GHz or upper
Operating system Windows Seven Pro 32 Bits SP1, 2003 Server or XP
Pro SP3
2.2 PACiS SMT Kernel

Pro SP3
2.3 PACiS SMT Kernel (MiCOM A300)

Hard disk 3.82 Gbytes or more
CPU Intel(R) Pentium(R) M processor 1.8GHz
Pro SP3
2.4 PACiS GTW

Pro SP3
2.5 PACiS GTW (MiCOM A300)

Hard disk 3.82 Gbytes or more
CPU Intel(R) Pentium(R) M processor 1.8GHz
Pro SP3
2.6 PACiS ES

Pro SP3
PACiS SBUS Agency
MAINTENANCE
CONTENTS
2. REGISTRY KEYS 4
SBUS/EN MF/D10 Maintenance
BLANK PAGE

This document is a chapter of the PACiS Station BUS Agency documentation. It describes
the keys in the registry.
SBUS/EN MF/D10 Maintenance
2. REGISTRY KEYS
This chapter describes the key registered by the application, the use of this key and the
range value.
The installation procedure sets the two following register keys:
PACIS\61850Agency
PACIS\tunneling
NOTE : For the path access of registry keys, please consult the
Schneider Electric technical support if needed.
Which has the following values and explanation:
PACiS\61850Agency
Name Type Data Usage
DllDirectory REG_Z C:\Program Files\Pacis\ Where to find the
61850Agency\exe executable
DllName REG_Z OdRpc.dll name of the main DLL
ExeDirectory REG_Z C:\Program Files\Pacis\
61850Agency\exe
ExeName REG_Z Win32Agency.exe
ODFoundryDirectory REG_Z C:\Program Files\
Pacis\61850Agency\odfoundry
ODFoundryName REG_Z OdFoundry.exe
RpcPort REG_Z 8000
SrcDirectory REG_Z C:\Program Files\Pacis\
61850Agency\src
MVLLOG_ACSE REG_DWORD 1
MVLLOG_ACSEDATA REG_DWORD 0
MVLULOG_FLOW REG_DWORD 0
OdLogLevel REG_DWORD 1
PACiS\tunneling\install
DllDirectory REG_Z C:\Program Files\Pacis\ Where to find the
61850Agency\exe executable
DllName REG_Z PatuClient.dll
PACiS\tunneling\param
MonInterval REG_DWORD
MonTo REG_DWORD
RpcMonitoring REG_Z
toClose REG_DWORD
toOpen REG_DWORD
toSend REG_DWORD
Trace REG_Z
TraceLevel REG_DWORD
PACiS\tunneling\S1V2param
(by default) REG_Z (non defined value)
GLOSSARY
Page 1/14
CONTENTS

2. GLOSSARY 4
PACiS/EN LX/D10 Glossary
Page 2/14
BLANK PAGE
Page 3/14

This document is the last chapter of each PACiS documentation. It is the glossary.
Page 4/14
2. GLOSSARY
AC Alternating Current
AccI Accumulator Input
ACSI Abstract Communication Service Interface
Mapping from the standard IEC 61850 abstract specification of
communication service to a concrete communication infrastructure based
on CORBA.
A/D Analog/Digital
ADC Analog to Digital Converter
AE qualifier Application Entity qualifier
Used internally by IEC 61850 to identify a server application
AI Analog Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers, and
representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analog Input Unit ( C264 Bay Computer board name for DC Analog Input)
Alarm An alarm is any event tagged as an alarm during the configuration phase
AO Analog Output
Value corresponding to a desired output current applied to a DAC.
AOU Analog Output Unit ( C264 Bay Computer board name for Analog Output)
API Application Programming Interfaces
AR Auto-Reclose
ARS Auto-Recloser
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in the OSI protocol for applicable data (T103, T101..)
ASE Applied System Engineering
ATCC Automatic Tap Change Control
Automation in charge of secondary voltage regulation, more specific than
AVR
AVR Automatic Voltage Regulator
Automatic system used to regulate the secondary voltage by automatic
tap changer control (see ATCC). Set of features can be added, see
chapter C264 FT.
Bay Set of LV, MV or HV equipment (switchgears and transformers) and
devices (Protective, Measurement…) usually encompassing a Circuit
Breaker and ancillary devices, and controlled by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Inputs, that determine a
Digital Measurement, then a Measurement value (with specific invalid
code when coding is not valid). Each decimal digit is coded by 4 binary
digits.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be Mosaic
Panel, C264 LCD, usually associated with Remote/Local control.
BCU Bay Control Unit
Name given to the C264 controlling a bay. Usually in contrast to
Standalone.
Page 5/14
BI Binary Input (or Information)

Designation of already filtered data entered into the C264 Bay Computer
before they become SPS, DPS with time tag and quality attributes
BIU Basic Interface Unit
C264 board for auxiliary power supply, watchdog relay, redundancy I/O
BNC A connector for coaxial cable.
B-Watch Monitoring and control device for GIS substation.
CAD Computer Aided Design
Computer application dedicated to the design of wiring, for example.
CAS CASe
C264 Bay Computer rack
CAT Computer Administration Tool
CB Circuit Breaker
Specific dipole switch with the capability to make line current and break
fault current. Some have isolation capability, i.e. nominal grounding
(earthing) at each side.
CBC Compact Bay Controller
Small capacity Bay Computer for Medium Voltage applications, typically
C264C
CC Complemented Contact
CCU Circuit breaker Control Unit
C264 Bay Computer board dedicated to switch control with 8DI, 4 DO
CDM Conceptual Data Modeling
This is the modeling of system/devices data using a hierarchy of
structured data (called object or class) with their attributes, methods or
properties and the relations between each other. It maps common data to
devices or components of devices, with guarantee of interoperability.
Class Defined in IEC 61850 as: description of a set of objects that share the
same attributes, services, relationships, and semantics
Client Defined in IEC 61850 as: entity that requests a service from a server and
that receives unsolicited messages from a server
CM Commissioning
CMT Computer Maintenance Tool
CO Command, logic information Output (Functional Component) / Contact
Open
COMTRADE Common Format For Transient Data Exchange (international standard
IEC 60255-24)
CPU Central Processing Unit
C264 Bay Computer main board based on a Power PC
CRC Cyclic Redundancy Check
Coding result sent with packet of transmitted data to guarantee their
integrity. Usually result of a division of transmitted data by polynomial.
CSV Character Separate Values
ASCII values separated by a predefined character or string as in Excel or
ASCII Comtrade.
CT Current Transformer
Basically the electric device connected to process and extract a current
measurement. By extension, part of a device (C264) that receives an AC
value and converts it into a numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional) By extension, the C264 TMU board.
Page 6/14
CT/VT Current and Voltage transformers

(Non- New generation of transducer based for example on light diffraction under
Conventional or an electric field. Without transformer, gives a direct numerical
intelligent) measurement of voltage and current as a communicating IED.
CSV Character Separated Values
ASCII values separated by predefined character or string as in Excel or
ASCII Comtrade.
DAC Data Acquisition component of the GPT
DAC Digital to Analog Converter
Used to generate an analog signal (usually DC) from a digital value.
DB DataBase
Tool or set of data that defines the entire configuration of a system or
specific device such as a computer. In contrast to a setting or parameter,
the DB has a structure that cannot be modified on-line. DBs are always
versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications and
computer devices.
DBI Don’t Believe It
Term used for an undefined state of a double point when inputs are not
complementary. DBI00 signifies dynamic state or jammed. DBI11 signifies
undefined.
DBID Databases Identity Brick
DC Direct Current
DC, DPC Double (Point) Control
Two digits and/or relay outputs used for device control with
complementary meaning (OPEN, CLOSE).
DCF77 External master clock and protocol transmission
LF transmitter located at Mainflingen, Germany, about 25 km south-east
of Frankfurt/Main, broadcasting legal time on a 77.5 kHz standard
frequency.
DCO Double Control Output
DCP Device Control Point
Located at device level (electric device or IED). It should have its own
Remote/Local switch.
DCS Digital Control System
Generic name of system based on numeric communication and devices,
to be opposed to traditional electrically wired control.
DCT Double Counter
Counter based on 2 DI with complementary states (counting switching
operations, for example)
DE Direct Execute
DELTA Phase-to-phase delta values
Device Term used for one of the following units:
Protective relays, metering units, IED, switchgear), disturbance or quality
recorders.
Switchgear: switching device such as a CB, disconnector or grounding
(earthing) switch
DHMI C264 Display HMI
DI Digital Input
Binary information related to the presence or to the absence of an external
signal, delivered by a voltage source.
Page 7/14
DIN Deutsche Institut für Normung

The German standardization body.
DIU DC Input Unit
C264 Bay Computer board name for Digital Input
DLL Dynamic Link Library. Available on Windows XP.
A feature that allows executable code modules to be loaded on demand
and linked at run time. This enables the library-code fields to be updated
automatically, transparent to applications, and then unloaded when they
are no longer needed.
DM Digital Measurement
A measurement value with acquisition by DI and a specific coding BCD,
Gray, 1-out-of-n, and so on.
DNP3.0 Distributed Network Protocol
DNP3 is a set of communication protocols used between components in
process automation systems.
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to
execute single or dual, transient or permanent, commands.
DOF Degree Of Freedom
Used for a template attribute that can be modified or not when used. An
attribute has a degree of freedom if a user can modify its values on its
instances
DOU Digital Output Unit
C264 Bay Computer board name for Digital Output
DP Double Point
Information/control derived from 2 digital inputs/output; usually employed
for position indication of switching devices (OPEN, CLOSE).
DPC Double Point Control
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
ECDD Coherent Extract of Distributed Data
ECU Extended Communication Unit.
External module connected to the CPU board. This module converts non-
insulated RS232 into optical signal or insulated RS485/RS422.
EH90 Transmission protocol dedicated to time synchronization and standardized
by EDF. Specification document: D.652/90-26c, March 1991.
EMC Electro-Magnetic Compatibility
EPATR Ensemble de Protection Ampèremétrique de Terre Résistante (French
legacy: very resistive earth current module)
Event An event is a time-tagged change of state/value, acquired or transmitted
by a digital control system.
EWS Engineering Workstation
FAT Factory Acceptance Test
Validation procedures execution with the customer at factory.(i.e. SAT)
FBD Functional Block Diagram
One of the IEC 61131-3 programming languages (language used to define
configurable automation).
FIFO First In First Out
FO Fiber-Optic
FP Front Panel
Page 8/14
FTP Foil Twisted Pair

FLS Fast Load Shedding
FSS Force Suppress Substitute
Gateway Level 6 session of OSI, the gateway is any device transferring data
between different networks and/or protocols. The RTU function of the
C264 gives a gateway behavior to SCADA or RCP level. PACiS Gateway
is separate PC base device dedicated to this function.
GHU Graphic Human interface Unit
C264 Bay Computer Front Panel digital part (LCD, buttons, Front RS)
GIS Gas Insulated Substation
GLOBE GLOBE Brick
GMT Greenwich Mean Time
Absolute time reference
GPS Global Positioning System
Based on triangulation from satellite signals.
Also transmits absolute GMT time used to synchronize a master clock
GOOSE Generic Object Oriented Substation Event
GPT Generic Protocol Translator software, supplied by ASE
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
GSSE Generic Substation Status Event
Hand Dressing Facility for an operator to set the position of a device manually (position
acquired by other means) from the HMI at SCP level; e.g. from OPEN to
CLOSE (without any impact on the “physical” position of the electrical
switching device).
HELPS Hostable Emulator for Load and Protocol Simulation. HELPS simulates
an Intelligent Electronic Device (IED)
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be PACiS OI (Operator Interface) or C264 LCD (Local Control
Display) or set of LEDs, mosaic...
HSR High Speed Auto-Recloser, first cycles of AR
HTML Hyper Text Mark-up Language
Used as standard format for web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
ICD IED Capability Description
IEC International Electro-technical Commission
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based products
for data collection and information processing
IP Internet Protocol
IRIG-B Inter-Range Instrumentation Group standard format B. This is an
international standard for time synchronization based on an analog signal.
Page 9/14
JAMMED Invalid state of a Double Point:

Occurs when two associated digital inputs are still in state 0 after a user-
selected delay, i.e. when the transient state “ motion ” is considered as
ended
Kbus Term used for the Courier protocol on a K-Bus network (RS 422 type).
(Kbus Courier)
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols that are used to
communicate between C264 (Legacy Gateway function) and IED on field
bus. Networks are based on (RS232,) 422, 485. Protocols are IEC 60850-
5-103 (T103 or VDEW), Modbus Schneider Electric or MODICON
LCD Liquid Crystal Display or Local Control Display (on C264)
LD Ladder Diagram, one of the IEC 1131-3 programming languages
(language used to define configurable automation).
LED Light Emitting Diode
LF Low Frequency
LOC Local Operator Console
Dedicated to maintenance operation
L/R Local / Remote
Local / Remote When set to local for a given control point, it means that the commands
Control Mode can be issued from this point, or in remote control from higher-level
devices.
LSB Least Significant Bit
LSP Load Shedding Pre-Selection
LV Low Voltage
MAFS Marketing And Functional Specification
MC Modular Computer
MCB Mini Circuit Breaker. Position associated to the tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in IEEE 802.3
Measurements Values issued from digital inputs or analog inputs (with value, state, time
tag)
Metering Values computed depending on the values of digital or analog inputs
(non-tariff) during variable periods of time (time integration).
Metering Values computed depending on the values of digital or analog inputs
(tariff) during variable periods and dedicated to the energy tariff. These values
are provided by dedicated “tariff computers” external to the MiCOM
Systems.
MIDOS Schneider Electric Connector: Used for CT/VT acquisition
MMC Medium Modular Computer
MMS Manufacturing Message Specification (ISO 9506)
Modbus Communication protocol used on secondary networks with IED or with
SCADA RCP. 2 versions. Standard MODICON or Schneider Electric.
Module Word reserved in PACiS SCE for all electric HV devices. It groups all
switch-gear devices, transformers, motors, generators, capacitors, …
Page 10/14
MOTION Transient state of a Double Point

Occurs when the two associated digital inputs are momentarily in state 0
(e.g. position indication when an electrical device is switching). The
concept of “momentarily” depends on a user-selectable delay.
MPC Protection Module for Computer
MV Medium Voltage
MVAR Mega Volt Ampere Reactive
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OBS One-Box Solution
Computer that provides protection and control functions with local HMI.
The prime application of this device is intended for use in substations up
to distribution voltage levels, although it may also be used as backup
protection in transmission substations. Likewise, the OBS may be applied
to the MV part of a HV substation that is being controlled by the same
substation control system.
OI Operator Interface
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing
objects.
OLTC On Line Tap Changing
OMM Operating Mode Management
OPC OLE for process control
OPC is a registered trademark of Microsoft, and is designed to be a
method to allow business management access to plant floor data in a
consistent manner.
Operation hours Sum of time periods during which, a primary device is running in the
energized state. For example, a circuit breaker is in Closed state and the
current is not equal to 0 A.
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network,
transport, session, presentation, application
OWS Operator WorkStation (PACiS OI)
PACiS Protection, Automation and Control Integrated Solutions
PLC Programmable Logic Control /Chart. Includes PSL and ISaGRAF.
The configurable control sequences or automations taken into account by
the MiCOM Systems are defined within the PLC program.
POW Point On Wave
Point on wave switching is the control process of the three poles of an
HV-circuit breaker in a manner that to minimizes the effects of switching.
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
RCC Remote Control Centre
Computer or system that is not part of a MiCOM system. RCC
communicates with and supervises a MiCOM system using a protocol.
Page 11/14
RCP Remote Control Point

Name given to the device or part used to control remotely several bays or
sub-stations. Usually associated with Remote/Local sub-station control. It
is a SCADA interface managed by the MiCOM system through the
Telecontrol BUS. Several RCPs can be managed with different protocols.
Remote Control When set for a control point, it means that the commands are issued from
Mode an upper level and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may
provide all or part of functions handled by the substation HMI.
RI Read Inhibit
This output indicates the availability of an analog output (e.g. during DAC
converting time)
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RSE Régime Spécial d’Exploitation
French grid function when work is being done on an HV feeder
RSVC Re-locatable Static VAR Compensator
RS-232 Recommended Standard 232
A standard for serial transmission between computers and peripheral
devices.
RS-422 A standard for serial interfaces that extends distances and speeds beyond
RS 232. Is intended for use in multipoint lines.
RS-485 A standard for serial multipoint communication lines.
RS 485 allows more nodes per line than RS 422.
RSVC Re-Locatable Static Var Compensator
RTC Real Time Clock
RTU Remote Terminal Unit
Stand-alone computer that acquires data and transmits them to RCP or
SCADA. Typically it is the C964. RTU link is the TBUS.
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBMC Site Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands issued
from RCP. Moreover, some of its digital points & measurements (defined
during the configuration phase) are not sent to the RCP anymore (they are
“automatically” suppressed).
SBO Select Before Operate
A control made in two steps, selection and execution. The selection phase
gives a feedback. It can be used to prepare, reserve during time,
configure a circuit before execution. Controls are done into a protocol, or
physically (select with DI Select then DO execute).
S-BUS Station Bus, network between PACIS devices.
SCADA Supervisory Control And Data Acquisition
Equivalent to RCC
SCD Description file extension
SCE System Configuration Editor
SCL Substation automation system Configuration Language ( IEC 61850-6)
Page 12/14
SCP Substation Control Point

Name given to the device or part used to control several bays or
substation locally. Usually associated with Remote/Local substation
control. It is commonly the PACiS Operator Interface.
SCS Substation Control System
SCSM Specific Communication Service Mapping
SCT Single Counter
SER Sequence of Event Recorder
Combines SOE with accurate Time synchronization and Maintenance
facilities over Ethernet communication
Server Defined in IEC 61850 as: entity that provides services to clients or issues
unsolicited messages
Setpoints Analog setpoints are analog outputs delivered as current loops. Analog
(analog) setpoints are used to send instruction values to the process or auxiliary
device
Setpoints Digital values sent on multiple parallel wired outputs. Each wired output
(digital) represents a bit of the value. Digital setpoints are used to send instruction
values to the electrical process or to auxiliary devices.
SFC Sequential Function Chart
One of the IEC 1131-3 programming languages (language used to define
configurable automation).
SI System Indication
Binary information that does not come from an external interface. It is
related to an internal state of the computer (time status, hardware faults,
and so on). It is the result of all inner functions (AR, …), PSL, or ISaGRAF
automation.
SICU 4 Switchgear Intelligent Control Unit
Control unit of an intelligent circuit breaker (fourth generation)
SIG Status Input Group
SINAD Signal-plus-Noise-plus-Distortion to Noise-plus-Distortion ratio, in dB
SIT Status Input Double Bit
SMT System Management Tool
SNTP Simple Network Time Protocol
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
ST Structured Text
An IEC 1131-3 programming languages to define configurable automation
STP Shielded Twisted Pair
Substation Bay computer used at substation level
computer
SUI Substation User Interface
Suppression A binary information belonging to a bay in SBMC mode will be
(Automatic) automatically suppressed for the remote control. However changes of
state will be signaled locally, at SCP
Suppression A binary information can be suppressed by an order issued from an
(Manual) operator. No subsequent change of state on “suppressed information ”
can trigger any action such as display, alarm and transmission
Page 13/14
SWR Switch Redundant

C264 Bay Computer board Ethernet switch with redundant Ethernet
SWU Switch Unit ( C264 Bay Computer board Ethernet switch)
T101 Term used for IEC 60870-5-101 protocol
TBC / TBD To Be Completed / Defined
T-BUS Telecontrol Bus, generic name of networks and protocols used to
communicate between PACiS Gateway or C264 Telecontrol Interface
function and the RCP. Networks are based on RS 232, RS 485 or
Ethernet (T104). Protocols are IEC 60850-5-101 (T101), Modbus
MODICON
TC True Contact
TCIP Tap Change in Progress
TCU Transformer Current Unit
C264 Bay Computer CT/VT board : Current acquisition
TDD Total Demand Distortion, similar to the THD but applied to currents and
with a rated current (In) as reference
TG Telecontrol Gateway
THD Total Harmonic Distortion, sum of all voltage harmonics
TI Tele Interface
TM Analog Measurement
TMU Transducer-Less Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information of
interlocking the switchgear arrangement in the HV network, the switchgear type and
position, and defined rules for controlling this kind of switch (e.g. continuity
of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TS Logic position
TVU Transformer Voltage Unit

C264 Bay Computer CT/VT board : Voltage acquisition
UCA Utility Communications Architecture
Communication standard (mainly US) used for PACiS SBUS
communication
UPI Unit Per Impulse
Parameter of counter to convert number of pulses to Measurement value.
Both data (integer and scaled floating) are in a common class UCA2
Accumulator.
UTC Universal Time Co-ordinates (or Universal Time Code)
This designation replaces GMT (but it is practically the same for our
purposes).
VdBS Versioned data Base System, databag generated by SCE & ready to
download
VDEW Term used for IEC 60870-5-103 protocol
VDU Visual Display Unit
VMGA Vertical Measurement Graphical Area
Page 14/14
Voltage level Set of bays, whose plants & devices deal with the same voltage (for
example, 275 kV)
VT Voltage Transformer
Electric device connected to process and extract a voltage measurement.
By extension, part of a device (C264) that receives this AC value and
converts it to a numerical measurement value. VTs are wired in parallel.
WTS Windows Terminal Server, Microsoft remote desktop connection

WYE Three phases + neutral AI values
xPC Single Point Control, Double Point Control
Customer Care Centre
http://www.schneider-electric.com/CCC
© 2013 Schneider Electric. All rights reserved.
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone: +33 (0) 1 41 29 70 00
Fax: +33 (0) 1 41 29 71 00
www.schneider-electric.com Publishing: Schneider Electric
Publication: SBUS/EN T/D10 02/2013

Pacis Sbus Agency: Sbus/En T/D10

Uploaded by

Copyright:

Available Formats

Pacis Sbus Agency: Sbus/En T/D10

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pacis Sbus Agency: Sbus/En T/D10

Uploaded by

Copyright:

Available Formats

PACiS SBUS AGENCY

PACiS SBUS Agency Page 1/2

PACiS STATION BUS AGENCY IEC 61850

Safety & Handling SBUS/EN SA/D10

Introduction SBUS/EN IT/D10

Installation SBUS/EN IN/D10

Settings SBUS/EN ST/D10

Commissioning SBUS/EN CM/D10

Applications SBUS/EN AP/D10

Functional Description SBUS/EN FT/D10

Technical Data SBUS/EN TD/D10

Maintenance SBUS/EN MF/D10

Glossary PACiS/EN LX/D10

Page 2/2 PACiS SBUS Agency

PACiS SBUS Agency

SAFETY & HANDLING

PACiS SBUS Agency Page 1/8

1. SCOPE OF THE DOCUMENT 3

4. COPYRIGHTS & TRADEMARKS 6

5. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC

Page 2/8 PACiS SBUS Agency

PACiS SBUS Agency Page 3/8

1. SCOPE OF THE DOCUMENT

Page 4/8 PACiS SBUS Agency

PACiS SBUS Agency Page 5/8

Page 6/8 PACiS SBUS Agency

4. COPYRIGHTS & TRADEMARKS

PACiS SBUS Agency Page 7/8

5. WARNINGS REGARDING USE OF SCHNEIDER ELECTRIC PRODUCTS

Page 8/8 PACiS SBUS Agency

PACiS SBUS Agency

PACiS SBUS Agency Page 1/6

2. INTRODUCTION TO PACiS SBUS AGENCY' GUIDE 4

3. INTRODUCTION TO PACiS SBUS AGENCY 5

Page 2/6 PACiS SBUS Agency

PACiS SBUS Agency Page 3/6

Page 4/6 PACiS SBUS Agency

2. INTRODUCTION TO PACiS SBUS AGENCY' GUIDE

PACiS SBUS Agency Page 5/6

3. INTRODUCTION TO PACiS SBUS AGENCY

Page 6/6 PACiS SBUS Agency

PACiS SBUS Agency

PACiS SBUS Agency Page 1/10

1. SCOPE OF THE DOCUMENT 3

Page 2/10 PACiS SBUS Agency

PACiS SBUS Agency Page 3/10

1. SCOPE OF THE DOCUMENT

Page 4/10 PACiS SBUS Agency

Check/Configure the user account type:

PACiS SBUS Agency Page 5/10

To install PACiS SBUS, do following:

• Choose the Language

• Click Next in the Wizard.

Page 6/10 PACiS SBUS Agency

• Read the License Agreement, select I accept the agreement

PACiS SBUS Agency Page 7/10

• Select if first install or not (First installation by default)

Page 8/10 PACiS SBUS Agency

• Check that the proposed settings are the correct ones