Baseline Software Platform

IEC103 Device (Master)

05/2016

www.schneider-electric.com
 Rev. 1.2 (20-05-2016)

Change Control
Rev Date Description

1.1 30-03-2016 Initial revision for Easergy Builder.

1.2 20-05-2016 Reviewed IEC103 master profile.

Relevant information for the user

As a result of the multiple uses of the product, the personnel in charge of the application and use of this control device
must ensure these usages comply with all safety and performance requirements applicable in each application. The
requirements include the applicable industry-related laws, norms, regulations and standards.
Throughout this manual some notes are included in order to alert the user about specific circumstances:

NOTICE
NOTICE identifies information about practices and circumstances which could result in a malfunction of the equipment..

Restricted Liability
Electrical equipment should be serviced and maintained only by qualified personnel.
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this manual. This
document is not intended as an instruction manual for untrained persons.
The illustrations, dialog boxes, programming models and examples shown in this manual are intended for exemplary
purposes. As there are installation-specific variables and requirements, Telvent will not be held responsible for the misuse
of the equipment based on the examples herein published.

NOTICE
An inadequate use of the equipment, or misuse by ignoring these specifications, may comprise the system’s security.

It is highly recommendable to backup the application programs frequently using the appropriate storage media to avoid
potential data loss.

The Saitel platform and all its components have been developed in accordance to the requirements for a
quality management system, complying with the ISO 9001 Norm

Document: TE-HG-0000-IEC3-S854

Revision / Date: Rev 1.2 / 20-05-2016

File: IEC103 Master Device_EN_Rev1.2.pdf

Retention period: Permanent throughout its validation period + 3 years after its
cancellation.

Should the user have any request, problem report or suggestion about the equipment, the following email address is
available:
es-infoSaitel@schneider-electric.com

Configuring IEC103 Master 1

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

Table of Contents
Table of Contents .................................................................................................................................................................. 2
Index of Figures..................................................................................................................................................................... 3
Index of Tables...................................................................................................................................................................... 4
Manual Contents ................................................................................................................................................................... 5
Chapter 1. Easergy Builder & IEC103.......................................................................................................................... 1-1
1.1 Easergy Builder v1.0.20 ..................................................................................................................................... 1-2
1.1.1 Environment Description ............................................................................................................................ 1-2
1.1.2 Device Catalog ........................................................................................................................................... 1-3
1.2 Introduction to IEC103........................................................................................................................................ 1-4
1.2.1 Data Types ................................................................................................................................................. 1-4
Chapter 2. IEC103 Master............................................................................................................................................ 2-1
2.1 IEC103 Master Administration............................................................................................................................ 2-1
2.1.1 Signal Identification - Coordinates .............................................................................................................. 2-1
2.1.2 Diagnostic Coordinates .............................................................................................................................. 2-1
2.1.3 Relationship with coreDb............................................................................................................................ 2-2
2.2 IEC103 Master in Easergy Builder...................................................................................................................... 2-2
Chapter 3. IEC103 Master Profile ................................................................................................................................ 3-1
3.1 Physical layer ..................................................................................................................................................... 3-1
3.1.1 Electrical interface ...................................................................................................................................... 3-1
3.1.2 Optical interface.......................................................................................................................................... 3-1
3.1.3 Transmission speed ................................................................................................................................... 3-1
3.2 Link layer ............................................................................................................................................................ 3-1
3.3 Application layer ................................................................................................................................................. 3-1
3.3.1 Transmission mode for application data ..................................................................................................... 3-1
3.3.2 COMMON ADDRESS of ASDU.................................................................................................................. 3-1
3.3.3 Selection of standard information numbers in monitor direction ................................................................. 3-1
3.3.4 Selection of standard information numbers in control direction .................................................................. 3-3
3.3.5 Basic application functions ......................................................................................................................... 3-4
3.3.6 Miscellaneous............................................................................................................................................. 3-4
Glossary ................................................................................................................................................................................A

2 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Index of Figures
Figure 1-1. Baseline software architecture. ........................................................................................................................ 1-1
Figure 1-2. Relation between coreDb and other applications............................................................................................. 1-2
Figure 1-3. Startup window of Easergy Builder. ................................................................................................................. 1-2
Figure 1-4. Easergy Builder interface. ................................................................................................................................ 1-3
Figure 1-5. Catalog device window. ................................................................................................................................... 1-3
Figure 2-1. New Device...................................................................................................................................................... 2-3
Figure 2-2. Communication channel and address associated to the Device ...................................................................... 2-3
Figure 2-3. New IEC103 master Device ............................................................................................................................. 2-3
Figure 2-4. Configuration of an IEC103 master Device ...................................................................................................... 2-4

Configuring IEC103 Master 3

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

Index of Tables
Table 1-1. Reference manuals.............................................................................................................................................. 5
Table 1-2. Software versions which this manual applies....................................................................................................... 5
Table 1-3. Hardware/ Software compatibility. ....................................................................................................................... 5
Table 2-1. Coordinate mappings in coreDb (Diagnostic points)......................................................................................... 2-2
Table 2-2. Coordinate mappings in coreDb (Points). ......................................................................................................... 2-2

4 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Manual Contents
I. Objective
This manual provides information about the configuration of the IEC103 master device in Easergy Builder.

II. Arrangement
This manual is divided in the following chapters.

Chapter 1 – Easergy Builder & IEC103

This chapter describes the main elements and software architecture of the Baseline Software Platform.It gives a general
description of the tool Easergy Builder and IEC103.

Chapter 2 – IEC103 Master

Description of the user interface implemented in Easergy Builder to manage the information associated to master profile of
the IEC103 communication protocol.

III. Reference Manuals

The following documents, which could be used for further reference, are provided to supplement the information included
in this manual:

Manual’s name Document

Easergy Builder User Manual TE-HG-0000-MSS-S856

Saitel Webtool User Manual TE-HG-0000-MCW-S856

Table 1-1. Reference manuals

IV. Software Versions

The information in this manual applies to software versions listed in the following table and subsequent:

Module Software version (CPU) Pluging version (Easergy Builder)

IEC103 master I3mBinC - 10.00.03 IEC103M – 1.0.9.0

Table 1-2. Software versions which this manual applies

V. Hardware/Software Compatibility
Controllers supported by the CPU modules of different hardware platforms are the following:

Bin Controller SM_CPU866 SM_CPU866e HU_B/HU_BI HU_A/HU_AF HU 250

Easergy Builder √ √ √ √ √

IEC103 master √ √ × √ √

Saitel Webtool √ √ × √ ×
Table 1-3. Hardware/ Software compatibility.

Configuring IEC103 Master 5

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Chapter 1. Easergy Builder & IEC103

The Baseline Software Platform of Schneider Electric is composed by:
 VxWorks & Linux operating systems.
 Real-time applications and its configuration files.
 Configuration, management, supervision and monitorization tools.

NOTICE
Saitel DR basic heads (modules HU_B and HU_BF) don’t load VxWorks nor Linux. They operate with a tailored-made
software which includes the OS, database and applications.

The following figure shows the different applications included in the software platform, as well as additional applications
that implement protocols to upgrade Easergy Builder:

Figure 1-1. Baseline software architecture.

The operating system abstracts the hardware from the software applications and manages the applications in real time. It
integrates the basic protocols to access the remote unit (SFTP, SSH, etc.) and manage multiple users.
The real-time database, named coreDb, is probably the most important element. All the other elements are developed
around coreDb:

Configuring IEC103 Master 1-1

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

Figure 1-2. Relation between coreDb and other applications.

coreDb performs the real-time management of RTU signals. This real-time database is associated with data producing
and consuming Devices. Devices are the different data acquisition and processing applications software which access
coreDb.
For more information about the Baseline Software Platform, please consult the manuals “Easergy Builder User Manual”
and “Saitel Webtool User Manual”.

1.1 Easergy Builder v1.0.20

1.1.1 Environment Description
The access to Easergy Builder is done through the Windows® Home Menu, or through the direct access created on the
desktop.

Figure 1-3. Startup window of Easergy Builder.

The initial interface is as follows:

1-2 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Figure 1-4. Easergy Builder interface.

The Easergy Builder image depend on if there is a configuration active or not. For example, the previous figure shows
Easergy Builder when you are editing a configuration:
 1: Information about the active configuration.
 2: Toolbar and main menu.
 3: Edition zone.
 4: Log console
 5: Device catalog
The toolbar, main menu and edition zone will be detailed for each device.

1.1.2 Device Catalog

Editing a configuration, select the tab “Devices” in the zone 2 in order to show information about the devices available in
your PC. At the right of the zone 2 you can see the catalog device window:

Figure 1-5. Catalog device window.

This window shows all configurations that have been stored as a template. More information about this tool in the Easergy
Builder user manual.

Configuring IEC103 Master 1-3

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

1.2 Introduction to IEC103

The IEC-60870-5-103 communication protocol defines a “controlling station” and a “controlled station” which are usually
named as “master” and “slave” respectively. The IEC103 master device implements the protocol of the “controlling
station”.
ASDU (Application Service Data Unit) is the name of the data unit exchanged between the “controlled station” and the
“controlling station” at the application layer. There must be at least one ASDU defined for each information point controlled
by this protocol
Each point in this protocol is identified with two 1-byte values (FUNCTION TYPE, INFORMATION NUMBER). For some
ASDU type (for measurements) several points are sent with the same couple (FUNCTION TYPE, INFORMATION
NUMBER) and the unique identifier for the point is the position into the ASDU.
Some protection types (i.e. ABB_REB500) include the “Common Adrress of ASDU” in the point identifier.

1.2.1 Data Types

IEC103 contains the following point types:
 IN: Digital or analog point.
 INC_C: Fleeting digital or analog point.
 IN_D: Digital or analog input that must be handled as double.
 OUT_ON: Digital or analog output. Always the value ON (10) is sent.
 OUT_OFF: Digital or analog output. Always the value OFF (01) is sent.
 OUT_S: Digital or analog output. If the value of the command in coreDb is ‘1’, the value ON (10) is sent. If the
value en coreDb is ‘0’, the value in OFF (01) is sent.
 OUT_D: Digital or analog output. Having in account the value of the command in coreDb, the two least significant
bits are sent.

1-4 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Chapter 2. IEC103 Master

2.1 IEC103 Master Administration
2.1.1 Signal Identification - Coordinates
The point coordinates for the IEC103 device have the following format:

Coordinate for IEC103 master device TIPO[:Axxx]:Fxxx:Pxxx:[Ixx][:M]

Where:
 TIPO: Type of entry.
o IN: Digital or analog input.
o IN_C: Fleeting analog or digital input. Only the value “1” is received. The signal will set automatically to “0”
after a time.
o IN_D: Digital or analog input that will be considered as double digital.
o OUT_ON: Digital or analog output. The output value always will be ON (10), the value in coreDb is ignored.
o OUT_OFF: Digital or analog output. The output value always will be OFF (01), the value in coreDb is
ignored.
o OUT_S: Digital or analog output. If the command value in coreDb is “0”, the output value will be OFF (01). If
the command value in coreDb is “1”, the output value will be ON (10).
o OUT_D: Digital or analog output. The two least significant bits of the command value in coreDb will be sent.
 Axxx: It indicates the “Common Address of ASDU” of the point. This field is necessary if the field “USE
COMMON ADDRESS ASDU TO IDENTIFY POINTS” in Easergy Builder is checked. If not, this field doesn’t
included in the coordinate.
 Fxxx: FUNCTION TYPE in the ASDU. It is used for identify the point.
 Pxxx: INFORMATION NUMBER in the ASDU. It is used for identify the point.
 Ixx: This value is required only when the point is received in an ASDU with several points more. The value xx
indicates the position into the message.
 M: This field only is used with analog and digital outputs. It defined the coordinate as private, where are “Cause
of transmission 129” and “Type of ASDU 232”.
Coordinate examples for inputs: “IN:F160:P64” “IN_C:A1:F160:P64” “IN_D:F160:P144:I2”.
Coordinate examples for outputs: “OUT_ON:F160:P16” “OUT_OFF:A1:F160:P17” “OUT_S:F160:P232:M”,
“OUT_D:F160:P18”.

2.1.2 Diagnostic Coordinates

Some diagnostic information related to the Bin Controller should be reflected in the coreDb by means of information
points, so that this information is available for the rest of the processes. The coordinates which identify these point types
will have the format “DIAG:XX···X” where “XX···X” is a mnemonic that makes reference to the diagnostic information. The
current implementation defines the following diagnostic coordinates.
 DIAG:SERV: “1” indicates that the sector is “online” and “0” indicates that the sector is “offline”. A sector is online
when the associated slave has established the link, and has completed a general polling process. A sector is
offline when the associated slave doesn’t receive a valid response in any of the polling retries defined.
 DIAG:FC1 and DIAG:FC2: They are the coordinates for diagnostic signals which are used to control the status of
the communication channels. They are only applicable when duplicated channels are used (a LINK with two
associated channels).
Channels are switched when reaching half of the retries defined. If it is 0 (there are no retries and at every link
time-out it becomes unoperational) channels are switched at every time-out. If the LINK has a non-zero
TIME_FORCE_SWITCH, channels will be switched at the defined interval, regardless time-out. This is necessary
to keep channel status updated, in the absence of errors in the active channel.
o DIAG:FC1: If the value turns to “0”, it indicates that the communication through the first LINK channel has
logged a fault (i.e. half of the retries do not have response). It will become “1” again when a valid message is
received from this channel.

Configuring IEC103 Master 2-1

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

o DIAG:FC2: If the value turns to “0”, it indicates that the communication through the second LINK channel has
logged a fault (i.e. half of the retries do not have response). It will become “1” again when a valid message is
received from this channel.
 DIAG:COMM_OK: It is active when all sessions are in service.
The table below includes the possible mappings (grey boxes indicate the recommended mapping):
 Grey boxes: Recommended mapping.
 D: Has to be defined as “destination”.
 S: Has to be defined as “source”

Diagnostic points

Coordinates STATUS ANALOG COMMAND SETPOINT

DIAG:SERV S S

DIAG:FC1 S S

DIAG:FC2 S S

DIAG:COMM_OK S S

Table 2-1. Coordinate mappings in coreDb (Diagnostic points).

2.1.3 Relationship with coreDb

Possible Mappings
Once the coordinates’ format is defined, the user needs to determine the point types (according to the coreDb) and the
mode (source or destination) allowed for coordinates.
As a general rule, the points Command and Setpoint can be the destination for “control” coordinates of a IEC103M Device.
On other hand, a IEC103M Device with “monitor” coordinates will be the source of the points Status and Analog.
The table below includes the possible mappings.

Points

Coordinates (Type) STATUS ANALOG COMMAND SETPOINT

IN S S

IN_C S S

IN_D S S

OUT_ON D D

OUT_OFF D D

OUT_S D D

OUT_D D D

Table 2-2. Coordinate mappings in coreDb (Points).

2.2 IEC103 Master in Easergy Builder

At the left side in the configuration view of Easergy Builder, you can see the Devices tree for the configuration that you are
defining.
Use the button "Add" or the right-button of the mouse (on the tree) for creating a new Device.

2-2 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Figure 2-1. New Device

Where:
 Type: Type of the new Device. For IEC103 master you must select “IEC103 Master Protocol”.
 Name: Name of the new Device (Only letter, numbers and ‘_’ character are allowed for the name). Max. 32
characters).
 Description (optional): Description of the new Device.

Figure 2-2. Communication channel and address associated to the Device

Previously, you need to have configured the communication channels. To do that, please consult the Easergy Builder user
manual.
Select the communication channel and address for this Device. The address for a Device must be unique into each
channel.
The new Device will be shown in the tree:

Figure 2-3. New IEC103 master Device

You can double click on the Device (or use the buttom Modify) in order to edit or consult the configuration.

Configuring IEC103 Master 2-3

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

Figure 2-4. Configuration of an IEC103 master Device

Where:
 RTU: Device’s name
 Channel: Communication channel associated to the Device.
 Link parameters:
o Address: Device’address into the communication channel. (Max. 255)
o Reset Link: Type of reset; “Reset of communication unit” or “Only reset FCB”.
o Retries: Maximum number of times to retry a sending before to consider that a device is offline. Between 1
and 255.
o Link timeout: Timeout in milliseconds for a reply before retransmitting. Between 1 and 4294967295.
o Interchar timeout: Time in millisecond between two characters when they form a message. Between 50 and
4294967295.
 Application Parameters:
o Common ASDU address: Common address ASDU. Usually it matches with the link address
o Log unknown points: When it is enabled, unknown points will be registered in the system log.
o Use common Address ASDU To identify Points: When it is enabled, the common address ASDU is
included in the identification of points.
o General Interrogation Period: General interrogation period (in second). Recommended value is 60 s.
Beetween 60 and 4294967.
o Synchronization Period: Time for synchronization (in second). When it is 0, there isn’t synchronization.
Beetween 0 and 4294967.
o Synchronization Adjust: Timestamp sent with the message (in millisecond). Beetween 0 and 59999.
o Fleeting Timeout: Optional parameter. Time for mark the fleeting points to “0” (in millisecond). Beetween 0
and 4294967295). Default value is 1000 ms.
o Offline period: Time expected to retry the communication after an offline (in second). Between 1 and
4294967.
o Application ACK Timeout: Timeout for confirmation (application level) (in second). Beetween 1 and
4294967.
o Application end timeout: Timeout for end of function (application level) (in second). Beetween 1 and
4294967.
 Max. log errors: Maximum number of messages to be written in the system log. (Max 65535)

2-4 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

Chapter 3. IEC103 Master Profile

3.1 Physical layer
3.1.1 Electrical interface
X EIA RS-485

X Number of loads 32 for one protection equipment

NOTE – EIA RS-485 standard defines unit loads so that 32 of them can be operated on one line. For detailed information
refer to clause 3 of EIA RS-485 standard.

3.1.2 Optical interface

Glass fibre
Plastic fibre
F-SMA type connector
BFOC/2,5 type connector

3.1.3 Transmission speed

X 9600 bit/s
X 19200 bit/s

3.2 Link layer

There are no choices for the link layer.

3.3 Application layer

3.3.1 Transmission mode for application data
Mode 1 (least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively in this companion standard.

3.3.2 COMMON ADDRESS of ASDU

X One COMMON ADDRESS OF ASDU (identical with station address)
X More than one COMMON ADDRESS OF ASDU

3.3.3 Selection of standard information numbers in monitor direction

System functions in monitor direction
INF Semantics
X <0> End of general interrogation
X <0> Time synchronization
X <2> Reset FCB
X <3> Reset CU
X <4> Start/restart
X <5> Power on

Status indications in monitor direction

INF Semantics
X <16> Auto-recloser active

Configuring IEC103 Master 3-1

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

X <17> Teleprotection active

X <18> Protection active
X <19> LED reset
X <20> Monitor direction blocked
X <21> Test mode
X <22> Local parameter setting
X <23> Characteristic 1
X <24> Characteristic 2
X <25> Characteristic 3
X <26> Characteristic 4
X <27> Auxiliary input 1
X <28> Auxiliary input 2
X <29> Auxiliary input 3
X <30> Auxiliary input 4

Supervision indications in monitor direction

INF Semantics
X <32> Measurand supervision I
X <33> Measurand supervision V
X <35> Phase sequence supervision
X <36> Trip circuit supervision
X <37> I>> back-up operation
X <38> VT fuse failure
X <39> Teleprotection disturbed
X <46> Group warning
X <47> Group alarm

Earth fault indications in monitor direction

INF Semantics
X <48> Earth fault L1
X <49> Earth fault L2
X <50> Earth fault L3
X <51> Earth fault forward, i.e. line
X <52> Earth fault reverse, i.e. busbar

Fault indications in monitor direction

INF Semantics
X <64> Start /pick-up L1
X <65> Start /pick-up L2
X <66> Start /pick-up L3
X <67> Start /pick-up N
X <68> General trip
X <69> Trip L1
X <70> Trip L2
X <71> Trip L3
X <72> Trip I>> (back-up operation)
X <73> Fault location X in ohms
X <74> Fault forward/line
X <75> Fault reverse/busbar
X <76> Teleprotection signal transmitted
X <77> Teleprotection signal received
X <78> Zone 1
3-2 Configuring IEC103 Master

Baseline 11.05.05
 Rev. 1.2 (20-05-2016)

X <79> Zone 2
X <80> Zone 3
X <81> Zone 4
X <82> Zone 5
X <83> Zone 6
X <84> General start/pick-up
X <85> Breaker failure
X <86> Trip measuring system L1
X <87> Trip measuring system L2
X <88> Trip measuring system L3
X <89> Trip measuring system E
X <90> Trip I>
X <91> Trip I>>
X <92> Trip IN>
X <93> Trip IN>>

Auto-reclosure indications in monitor direction

INF Semantics
X <128> CB ‘on’ by AR
X <129> CB ‘on’ by long-time AR
X <130> AR blocked

Measurands in monitor direction

INF Semantics
X <144> Measurand I
X <145> Measurands I, V
X <146> Measurands I, V, P, Q
X <147> Measurands IN, VEN
X <148> Measurands IL1,2,3, VL1,2,3, P, Q, f

Generic functions in monitor direction

INF Semantics
X <240> Read headings of all defined groups
X <241> Read values or attributes of all entries of one group
X <243> Read directory of a single entry
X <244> Read value or attribute of a single entry
X <245> End of general interrogation of generic data
X <249> Write entry with confirmation
X <250> Write entry with execution
X <251> Write entry aborted

3.3.4 Selection of standard information numbers in control direction

System functions in control direction
INF Semantics
X <0> Initiation of general interrogation
X <0> Time synchronization

General commands in control direction

INF Semantics
X <16> Auto-recloser on/off

Configuring IEC103 Master 3-3

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

X <17> Teleprotection on/off

X <18> Protection on/off
X <19> LED reset
X <23> Activate characteristic 1
X <24> Activate characteristic 2
X <25> Activate characteristic 3
X <26> Activate characteristic 4

Generic functions in control direction

INF Semantics
X <240> Read headings of all defined groups
X <241> Read values or attributes of all entries of one group
X <243> Read directory of a single entry
X <244> Read value or attribute of a single entry
X <245> General interrogation of generic data
X <248> Write entry
X <249> Write entry with confirmation
X <250> Write entry with execution
X <251> Write entry abort

3.3.5 Basic application functions

Test mode
Blocking of monitor direction
Disturbance data
Generic services
Private data

3.3.6 Miscellaneous
Measurands are transmitted with ASDU 3 as well as with ASDU 9. As defined in 7.2.6.8, the maximum MVAL can either
be 1,2 or 2,4 times the rated value. No different rating shall be used in ASDU 3 and ASDU 9, i.e. for each measurand
there is only one choice.
Measurand Max. MVAL = rated value times
1,2 or 2,4
Current L1 X X
Current L2 X X
Current L3 X X
Voltage L1-E X X
Voltage L2-E X X
Voltage L3-E X X
Active power P X X
Reactive power Q X X
Frequency f X X
Voltage L1 - L2 X X

3-4 Configuring IEC103 Master

Baseline 11.05.05
Rev. 1.2 (20-05-2016)

Glossary
ASDU Application Service Data Unit.

coreDb Real time database of the Baseline Software Platform.

CPU Unidad Central de Procesamiento.

DB Base de datos, también BD.

EN Idioma inglés.

HU_A Saitel DR advanced HU.

HU_AF Saitel DR advanced HU with acquisition.

HU_B Saitel DR basic HU.

HU_BF Saitel DR basic HU with acquisition.

IED Intelligent Electronic Device

I/O Input / Output.

ITB Intelligent Terminal Block.

LAN Local Area Network o también Red de Área Local

mm Milímetro.

PC Personal Computer u Ordenador personal.

PLC Programable Logic Controler.

RAM Random Access Memory.

Rev Revisión.

RTC Real Time Clock.

RTOS Real Time Operating System. Un sistema operativo se considera en tiempo real si se
puede garantizar que el tiempo de ejecución de una determinada tarea siempre es
menor que uno dado (dependiente del hardware).

RTU Remote Terminal Unit

SBO Select Before Operate

SCADA Supervisory Control and Data Acquisition

SM_CPU866 Saitel DP CPU (standard).

SM_CPU866e Saitel DP CPU (advanced).

SO Operating System o también Sistema Operativo.

SP Idioma español.

TCP Transport Control Protocol.

Configuring IEC103 Master A

Baseline 11.05.05
 Fax:
E-mail:
Phone:
Seville, Spain
C/ Charles Darwin s/n
Schneider Electric

+34 95 541 33 75
+34 95 492 09 92
www.schneider-electric.com

Parque Científico y Tecnológico de la Cartuja

es-infoSaitel@schneider-electric.com
Baseline Software Platform

© 2016 All rights reserved. The information contained in this document is confidential and is owned by Schneider Electric. It cannot

Rev. 1.2 - May 2016

be copied or distributed in any way, unless there is express written authorization by Schneider Electric. Although this information
was verified at the time of publication, may be subject to change without notice.