Anda di halaman 1dari 51

ESPECIFICACIONES DE CONEXIN

PARA EL ENVO DE DATOS


AL SITR DEL CDC

DIRECCIN DE OPERACIN

NDICE
1.
2.
2.1.

INTRODUCCIN....................................................................................... 3
REQUERIMIENTOS PARA EL REPORTE DE INFORMACIN ........................... 3
EQUIPOS DE ADQUISICIN DE DATOS...................................................... 3

2.2.

ENLACES Y PROTOCOLOS DE COMUNICACIONES ....................................... 3

2.3.

2.2.1.
2.2.2.

Protocolo TCP/IP .................................................................................. 3


Protocolo Serial .................................................................................... 4
EQUIPOS DE RED ASOCIADOS A UN ENLACE TCP/IP .................................. 4

2.4.

EQUIPOS DE RED ASOCIADOS A UN ENLACE SERIAL.................................. 5

2.5.

INFORMACIN A TRANSMITIR AL SITR DEL CDEC-SIC ............................... 5

2.6.

ACCESO E INSTALACIN DE EQUIPOS Y

VAS DE COMUNICACIN EN

DEPENDENCIAS DEL CDEC-SIC ................................................................. 5


2.7.

2.8.

PRUEBAS DE PUESTA EN SERVICIO........................................................... 6


2.7.1.
2.7.2.
2.7.3.

Prueba de Enlace:................................................................................. 6
Prueba Inicial: ...................................................................................... 6
Prueba Punto a Punto: .......................................................................... 6
COSTOS estimados INVOLUCRADOS.......................................................... 7

2.8.1.
Hosting ................................................................................................ 7
2.8.2.
Modificacin Base de Datos SCADA CDEC-SIC ......................................... 7
2.8.3.
Protocolo Serial: Dispositivo Mode ShaRE DEVICES ............................... 7
2.8.4.
Protocolo ICCP: LICENCIA SPECTRUM .................................................... 8
ANEXO 1.- CONFIGURACIN ENLACE TCP/IP ..............................................................10
ANEXO 2.PROTOCOLO ICCP: EJEMPLO CONFIGURACIN TABLAS BILATERALES ....11
ANEXO 3.CONFIGURACIN ENLACE SERIAL ........................................................14
ANEXO 4.PROTOCOLOS IEC 870-5-104/101 Y DNP3.0 TCP-IP/SERIAL: PERFILES ...15
ANEXO 5
PROTOCOLOS IEC 870-5-101 Y DNP3.0 SERIAL: DISPOSITIVO DERIVADOR 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

1. INTRODUCCIN
El presente documento complementa el Procedimiento DO Definicin de parmetros
tcnicos y para el envo de datos al SITR del CDEC-SIC y especifica las condiciones
tcnicas y administrativas para la conexin de los Coordinados al SITR del CDC.

2. REQUERIMIENTOS PARA EL REPORTE DE INFORMACIN


2.1.

EQUIPOS DE ADQUISICIN DE DATOS

El coordinado deber seleccionar su equipo de adquisicin de datos y/o sistema de


reporte, dependiendo del nmero de seales a reportar al SITR del CDEC-SIC. Esta
definicin es relevante a la hora de informar al CDEC-SIC el protocolo de transmisin
de datos y para seleccionar el ancho de banda o velocidad de transmisin de su(s)
enlace(s).
2.2.

ENLACES Y PROTOCOLOS DE COMUNICACIONES

Dependiendo de la transmisin de datos que el coordinado seleccione, el coordinado


deber instalar, ya sea con equipamiento propio o contratado, los sistemas del enlace
de comunicaciones requeridos para cumplir con la disponibilidad de la informacin
especificada en la NTSyCS.
2.2.1.

PROTOCOLO TCP/IP

En el caso de que la transmisin de datos sea a travs de un enlace TCP/IP, el


protocolo y ancho de banda debern ser:
Protocolo
DNP 3.0 TCP/IP
IEC 870-5-104

Ancho de Banda
128 kbps o Superior
128 kbps o Superior

En el caso que se defina el intercambio de informacin entre centros de control, el


protocolo deber ser ICCP sobre TCP/IP.
Protocolo
ICCP TCP/IP

Ancho de Banda
128 kbps o Superior

El enlace principal que el coordinado establezca entre sus instalaciones y el front end
del CDEC-SIC, deber llegar a las instalaciones del CPD de Synapsis ubicado en Av.
Eduardo Frei Montalva 2205 (ex Panamericana Norte), comuna de Independencia,
Santiago. En el caso de que el coordinado determine utilizar en forma adicional un
enlace de respaldo, el segundo enlace deber llegar a las instalaciones del CPD de

Especificaciones de conexin al SITR del CDEC-SIC

3 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Synapsis, ubicado en Santa Rosa 76, primer subterrneo, comuna de Santiago,


Santiago.
2.2.2.

PROTOCOLO SERIAL

En el caso de que la transmisin de datos sea a travs de una RTU (serial), el


protocolo y ancho de banda debern ser:
Protocolo
DNP 3.0 Serial
IEC 870-5-101

Ancho de Banda
1.200, 9.600 19.200 baudios
1.200, 9.600 19.200 baudios

El enlace que el coordinado establezca entre sus instalaciones y el Front-End del


CDEC-SIC, deber llegar a las instalaciones del CPD de Synapsis ubicado en Av.
Eduardo Frei Montalva 2205 (ex Panamericana Norte), comuna de Independencia,
Santiago.
2.3.

EQUIPOS DE RED ASOCIADOS A UN ENLACE TCP/IP

En el caso de tratarse de una conexin de red Ethernet, la conectividad entre los


equipos ser habilitada y validada por las dos partes en conjunto, tanto por el
coordinado como por el CDEC-SIC a travs de Synapsis. Como paso previo a esta
habilitacin, el coordinado entregar un esquema de red con las direcciones IP y rutas
que deben ser configuradas y el CDEC-SIC lo complementar con sus propios
equipos, direcciones y rutas. En base a esta informacin, el CDEC-SIC generar un
diagrama unificado con los equipos de ambos, el cual considerar dispositivos
intermedios y cortafuegos que sean requeridos para establecer la conectividad.
En el ANEXO 1 se muestra un ejemplo que describe un diagrama esquemtico de
redes con los principales elementos que componen un enlace TCP/IP entre el CDECSIC y un coordinado. En l se indican las direcciones IP necesarias de los servidores
Front-End (TCS) e ICCP (UCS) del Sistema SIEMENS SPECTRUM del CDEC-SIC, as
como el firewall y el Switch de redes externas. Adems se muestran los equipos de
comunicaciones que integran este enlace.
En el ANEXO 4 se encuentran los perfiles de los protocolos TCP/IP IEC 870-5-104 y
DNP 3.0.
Especficamente para el protocolo ICCP, en el ANEXO 2 se encuentra un ejemplo de la
configuracin y parmetros de las tablas bilaterales que deben ser dispuestas en los
servidores de los centros de control.
Para el caso de un enlace TCP/IP, el CDEC-SIC indicar al coordinado el punto del
Switch de Redes Externas del SCADA del CDEC-SIC donde deber conectar un cable
con extremo RJ-45.

Especificaciones de conexin al SITR del CDEC-SIC

4 de 19

CDEC-SIC
Direccin de Operacin

2.4.

Mayo de 2007

EQUIPOS DE RED ASOCIADOS A UN ENLACE SERIAL

En el caso de tratarse de una conexin serial, la conectividad entre los equipos ser
habilitada y validada por las dos partes en conjunto, tanto por el coordinado como por
el CDEC-SIC a travs de Synapsis. Como paso previo a esta habilitacin, el
coordinado entregar un esquema de comunicaciones y definicin de parmetros de
los equipos RTU y el CDEC-SIC lo complementar con sus propios equipos,
direcciones y rutas. En base a esta informacin, el CDEC-SIC generar un diagrama
unificado con los equipos de ambos, el cual considerar los dispositivos que
conformarn la conectividad.
En el ANEXO 3 se muestra un ejemplo que describe un diagrama esquemtico de
comunicacin con los principales elementos que componen un enlace serial entre el
CDEC-SIC y un coordinado.
En el ANEXO 4 se encuentran los perfiles de los protocolos Seriales referidos.
En el caso de una conexin va RTU en protocolo DNP 3.0 Serial o IEC 870-5-101, el
CDEC-SIC indicar al coordinado el punto del Front-End del SCADA del CDEC-SIC
donde deber conectar un cable DB-25. A su vez, el coordinado deber considerar un
dispositivo derivador denominado Modem Sharing Device que permite utilizar la
redundancia del Front-End del Sistema SCADA del CDEC-SIC. En el ANEXO 5 se
presenta la descripcin tcnica del dispositivo y el pin-out del Terminal DB-25
necesario.
2.5.

INFORMACIN A TRANSMITIR AL SITR DEL CDEC-SIC

De acuerdo a lo especificado en el PROCEDIMIENTO DO DEFINICIN DE


PARMETROS TCNICOS Y OPERATIVOS PARA EL ENVO DE DATOS AL SITR DEL
CDC, el coordinado deber informar al CDEC-SIC el listado de variables que reportar
y transmitir al Sistema SIEMENS SPECTRUM del CDEC-SIC.
2.6.

ACCESO E INSTALACIN DE EQUIPOS Y VAS DE COMUNICACIN


EN DEPENDENCIAS DEL CDEC-SIC

En el caso de que el coordinado requiera instalar equipos en dependencias del CDECSIC para habilitar una va de comunicacin, deber tener presente lo siguiente:
La administracin de los servicios de SITR del CDEC-SIC, se realizan a travs de un
contrato de outsourcing con SYNAPSIS IT LTDA, esto significa que los equipos
debern instalarse en un CPD de dicha empresa, ubicado en Panamericana Norte
2205, comuna de Independencia; y en caso de utilizar la redundancia (slo para
enlace TCP/IP) debern instalarse en el CPD de Synapsis IT LTDA., ubicado en Santa
Rosa 76, comuna de Santiago.

Especificaciones de conexin al SITR del CDEC-SIC

5 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Todas las instalaciones de equipamiento tienen soporte de gabinetes, llegada de


comunicaciones, electricidad con sistemas de respaldo, sistemas de extincin de
incendios y atencin de operadores ante fallas.
Toda instalacin de equipos en el CPD de Synapsis est con contrato de servicios,
cuya prestacin del servicio de hosting y Mantenimiento tiene un costo para el
coordinado.
Antes de instalar un equipo en el CPD, el coordinado deber contactar, por lo menos
con dos das de antelacin, a don Alvaro Olguin Bruna (amob@synapsis-it.com) o
Jorge Silva Escobar (jese@synapsis-it.com), ambos de Synapsis, fono: 02- 397 66 00,
Anexos: [68 65] [67 42] [68 94], solicitando autorizacin de ingreso al CPD de
Synapsis para efectuar instalacin de equipos.
Adems, el coordinado deber proveer la siguiente informacin con 24 horas de
antelacin.
-

Nombre y Rut del personal que ingresarn al CPD.


Empresa a la que pertenecen.
Motivo del ingreso.
Da y Hora en que se realizarn los trabajos.

Con esta informacin, Synapsis gestionar los permisos correspondientes para que el
coordinado pueda ingresar al CPD y efectuar sus trabajos.
2.7.

PRUEBAS DE PUESTA EN SERVICIO

Para el programa de pruebas para la puesta en servicio se debe seguir el siguiente


procedimiento:
2.7.1.

PRUEBA DE ENLACE:

A nivel de capa de enlace se debe constatar que los equipos comuniquen verificando
rutas y permisos de los sistemas.
2.7.2.

PRUEBA INICIAL:

Se configuran en ambos centros una Base de Datos reducida de Prueba a concensuar


entre el CDEC-SIC y el coordinado.
Se revisa que todos los cambios de las variables transferidas se procesen en forma
correcta en el SCADA del CDEC-SIC.
2.7.3.

PRUEBA PUNTO A PUNTO:

Especificaciones de conexin al SITR del CDEC-SIC

6 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Se configuran en ambos centros la Base de Datos definitiva y se realizan los cambios


de todas las variables que enva el coordinado.
2.8.
2.8.1.

COSTOS ESTIMADOS INVOLUCRADOS


HOSTING

Representa un Costo Fijo mnimo un (1) Ao y prorrogable automticamente por el


mismo periodo. El concepto de este costo es de utilizacin de espacio en gabinete,
energa con sistemas de respaldo, llegada de comunicaciones, sistemas de extincin
de incendios, atencin operadores y gestin de accesos. El valor por unidad de
espacio u durante un ao es de UF 25,0. Este costo debe quedar suscrito mediante
Contrato de Servicios de Hosting con Synapsis IT Ltda.
2.8.2.

MODIFICACIN BASE DE DATOS SCADA CDEC-SIC

Representa un Costo Variable hacia Synapsis IT Ltda., como administrador de la


plataforma SCADA Spectrum del CDEC-SIC. El costo depende del nmero de datos
que se deben integrar en el sistema SCADA. Se utilizarn precios histricos de
implementaciones similares y que estn en conocimiento por parte del CDEC-SIC. En
la siguiente tabla se indican precios de acuerdo al nmero de Tags:
Alcance General Servicios
Configuracin Tablas Interfaz
Pruebas:
Integracin Enlace
Transmisin de Datos
Desarrollo Base de Datos:
SCADA
Histrica
Modelo Aplicaciones
Pruebas Punto a Punto
TOTAL UF

Nmero de Tags
N 25

25 < N 50

50 < N 80

80 < N 120

120 < N

10

12

14

20

28

25

40

68

84

Revisar
Caso a Caso

10

14

22

49

68

102

132

Revisar
Caso a Caso
Revisar
Caso a Caso

Precios sujetos a revisin y con fines presupuestarios.


Plazos de Ejecucin: 3 semanas una vez aceptada la oferta.
Garanta: 2 meses, despus de la puesta en servicio.
No incluye ningn equipo hardware, Licencia, ni enlace de comunicaciones.
Se debe agregar 10% de administracin.
Los precios no incluyen IVA.

2.8.3.

PROTOCOLO SERIAL: DISPOSITIVO MODE SHARE DEVICES

Representa un Costo de Activacin para el coordinado que decida comunicar con


protocolos seriales (IEC 870-5-101 y DNP3.0 serial). Consiste en un dispositivo de
comunicaciones que permite obtener redundancia en el Front-End concentrador de
comunicaciones del CDEC-SIC (ver esquema ANEXO 3 y especificaciones en ANEXO
5). Este dispositivo es suministrado por Synapsis y tiene un costo estimado de: USD$
260.-

Especificaciones de conexin al SITR del CDEC-SIC

7 de 19

CDEC-SIC
Direccin de Operacin

2.8.4.

Mayo de 2007

PROTOCOLO ICCP: LICENCIA SPECTRUM

Representa un Costo de Activacin para el coordinado que decida comunicar con


protocolo ICCP. Consiste en una licencia de conectividad y habilitacin lgica en el
sistema SCADA Spectrum del CDEC-SIC. El costo estimado de la licencia es de: USD$
7.850.-

NOTA IMPORTANTE: Protocolo IEC104 MAESTRO


El Coordinado debe tener en consideracin que el front-end IEC104 del SCADA del
CDEC-SIC es un servidor Maestro, esperando de forma estndar iniciar la
comunicacin con una RTU.
En caso de que el Coordinado requiera conectar un equipo concentrador (como un
sistema de control numrico), debe solicitar una reunin tcnica con los especialistas
de Synapsis para valorizar dicha integracin.

Especificaciones de conexin al SITR del CDEC-SIC

8 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

ANEXOS
ANEXO 1.-

CONFIGURACIN ENLACE TCP/IP

ANEXO 2.-

PROTOCOLO ICCP: EJEMPLO CONFIGURACIN TABLAS BILATERALES

ANEXO 3.-

CONFIGURACIN ENLACE SERIAL

ANEXO 4.-

PROTOCOLOS IEC 870-5-104/101 Y DNP3.0 TCP-IP/SERIAL: PERFILES

ANEXO 5.-

PROTOCOLOS IEC 870-5-101 Y DNP3.0 SERIAL: DISPOSITIVO DERIVADOR

Especificaciones de conexin al SITR del CDEC-SIC

9 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

ANEXO 1.- CONFIGURACIN ENLACE TCP/IP

Red SCADA Coordinado

OPCIONES:
IP UTR IEC104 Coordinado: AA.BB.CC.DD
IP UTR DNP3.0 Coordinado: AA.BB.CC.DD
IP Servidor ICCP Coordinado: AA.BB.CC.DD

IP router lado LAN: AA.BB.CC.EE

Router

Enlace de Comunicacin 128 kbps o superior


IP router Lado WAN: FF.GG.HH.JJ

IP router lado WAN: FF.GG.KK.LL

SCADA CDEC-SIC
Instalaciones CPD Synapsis

Router

CPD Principal:

IP router lado LAN: 10.39.XX.YY

Edo. Frei Montalva 2205,


Comuna Independencia, Santiago

Switch
Redes Externas
Firewall: 10.39.XX.ZZ
IP(gateway) que resuelve acceso a servidores ICCP
del CDEC-SIC para SCADA del COORDINADO

CPD Respaldo:
Santa Rosa 76,
Comuna Santiago, Santiago
Firewall
SCADA

LAN A
LAN B

UCS1 LAN A: 10.39.8.9


UCS1 LAN B: 10.39.12.9
UCS2 LAN A: 10.39.8.10
UCS2 LAN B: 10.39.12.10

TCS1 LAN A: 10.39.8.15


TCS1 LAN B: 10.39.12.15

UCS1

TCS2 LAN A: 10.39.8.16


TCS2 LAN B: 10.39.12.16

TCS1
UCS2

TCS2

Notas:
TCS:

Tele-Control Server. Corresponde al servidor Front-End


del sistema SCADA Spectrum de SIEMENS del CDEC-SIC.

UCS:

Utility Communication Server. Corresponde al servidor ICCP


del sistema SCADA Spectrum de SIEMENS del CDEC-SIC.

Firewall:

Para ICCP se habilitar port 102 TCP.


Para DNP3.0 se habilitar port 20.000 TCP.
Para IEC104 port TCP a definir

Especificaciones de conexin al SITR del CDEC-SIC

10 de 19

CDEC-SIC
Direccin de Operacin

ANEXO 2.-

Mayo de 2007

PROTOCOLO ICCP: EJEMPLO CONFIGURACIN TABLAS


BILATERALES

En el caso de un enlace ICCP, el CDEC-SIC indicar al coordinado el nombre lgico del


enlace, nombre de los grupos de datos e identificador de los puntos que sern
transmitidos.
Asimismo, informar direcciones IP, lado iniciador del enlace y los
parmetros que se requieran para establecer la comunicacin.
La definicin de los parmetros de configuracin para un enlace ICCP se hace a travs de
un documento que el CDEC-SIC entregar al coordinado y que contiene la configuracin
de las tablas bilaterales, junto con la definicin del resto de los parmetros de red que
ICCP necesita para la configuracin de los servidores (selectores Tsel, Psel, etc.). Con esta
informacin, el coordinado deber aplicarla en su servidor ICCP.
Ejemplo Tabla Bilateral ICCP: Central RALCO.
Informacin general del Enlace
Un solo enlace de Datos Bidireccional
Parmetro
Nombre del sistema SCADA CDEC-SIC
Nombre del Centro de Control SCADA CDEC-SIC
Nmero Mximo de Transfer Sets
Nmero Mximo de Data Sets
Tamao Mximo de Mensajes MMS
Bloques MMS soportados
Nombre del Remoto (mirado desde SCADA CDEC-SIC)
Nombre del Centro de Control Remoto (mirado desde SCADA CDECSIC)
Iniciador de Requerimiento de Asociacin
Time Out del Requerimiento de Asociacin
Reintento de Requerimiento de Asociacin
Time Out del Reintento de Requerimiento de Asociacin
Versin de la Tabla Bilateral
Versin del ICCP
Nombre del Dominio Local (mirado desde SCADA CDEC-SIC)
Nombre del Dominio Remoto (mirado desde SCADA CDEC-SIC)
Nombre del LINK
Nmero del Canal
Nombre del AR Local
Nombre del AR Remoto Primario
Nombre del AR Remoto Alternativo

Especificaciones de conexin al SITR del CDEC-SIC

Valor
ICCP
MCS
400
400
15000
1y2
COORDINA
RALCO _DOMAIN
SCADA CDEC-SIC
18 seg.
8 seg.
10 seg.
SYNAPSIS
1996-08
DOMAIN_ COORDINA
DOMAIN_MCS
COORDINA
11
LOCAL_ COORDINA
REMOTE_ COORDINA

11 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Datos a adquirir por parte del SCADA CDEC-SIC como cliente


Informacin del grupo de datos reportados por excepcin y con transmisin de la estampa
de tiempo
Tipo de Dato: Data_StateExtended

Parmetro
Nombre del Grupo
Reporte Peridico de Datos
Reporte por Excepcin de Datos
Intervalo de Chequeo de Integridad

Valor
Excpt_1
No Aplica
S
600 seg.

Informacin del Grupo de Datos Reportados Peridicamente


Tipo de Dato: Data_RealQ

Parmetro
Nombre del Grupo
Reporte Peridico de Datos
Reporte por Excepcin de Datos
Periodicidad del Reporte de Datos

Especificaciones de conexin al SITR del CDEC-SIC

Valor
Perio_1
S
No Aplica
10 seg.

12 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Valores de Conexin o Selectores


(Sacado del archivo de configuracin del SCADA del CDEC-SIC)
Definicin del local:
Begin_Local
Common_Name
AP_Title
AP_InvokeID
AE_Qualifier
AE_InvokeID
Psel
Ssel
Tsel
Subnet
QOS
End_Local

= LOCAL_COORDINA
= 1 2 50 18
= 100
=2
=1
= 00000068
= 0001
= 0001
=0
=0

Definicin del remoto:


Begin_Remote
Common_Name
AP_Title
AP_InvokeID
AE_Qualifier
AE_InvokeID
Psel
Ssel
Tsel
Subnet
QOS
IP_ADDRESS
Transport
End_Remote

= REMOTE_ COORDINA
= 1 2 50 18
= 100
=2
=1
= 00000068
= 0001
= 0001
=0
=0
= ip servidor ICCP del COORDINADO
= TCP

Especificaciones de conexin al SITR del CDEC-SIC

13 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

ANEXO 3.- CONFIGURACIN ENLACE SERIAL

Red SCADA Coordinado


UTR IEC101 y/o DNP3.0 Serial Coordinado:
Enlace de Comunicacin 128 kbps o superior

Nombre UTR: SE Chile / Central Chile


Direccin Fsica: AA
Direccin Lgica: BB

SCADA CDEC-SIC
Dispositivo Comunicaciones
Por ejemplo: Mdem

Instalaciones CPD Synapsis


CPD Principal:
Edo. Frei Montalva 2205,
Comuna Independencia, Santiago

Dispositivo Derivador

RAN1

RAN2

LAN A
LAN B

TCS1
TCS2

Notas:
TCS:

Tele-Control Server. Corresponde al servidor Front-End


del sistema SCADA Spectrum de SIEMENS del CDEC-SIC.

RAN:

Remote Asynchronous Node. Corresponde al Switch


Concentrador de Comunicaciones del sistema SCADA
Spectrum de SIEMENS del CDEC-SIC.

Especificaciones de conexin al SITR del CDEC-SIC

14 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

ANEXO 4.- PROTOCOLOS IEC 870-5-104/101 Y DNP3.0 TCP-IP/SERIAL:


PERFILES

En el caso de una conexin va RTU, el CDEC-SIC indicar al coordinado las direcciones


lgicas dentro del protocolo asociadas a los puntos que sern transmitidos.
En el caso de una conexin TCP/IP, el CDEC-SIC indicar al coordinado las direcciones
lgicas dentro del protocolo asociadas a los puntos que sern transmitidos, as como
direcciones IP o direcciones de puertas fsicas, etc.

Especificaciones de conexin al SITR del CDEC-SIC

15 de 19

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Perfil IEC 870-5-104/101

Perfil
IEC-104-101.pdf

Especificaciones de conexin al SITR del CDEC-SIC

16 de 19

IEC-60870-5-101
______________________________________________________________________
1.1

Communication profiles

1.1.1 Protocol IEC870-5-101


This chapter contains the protocol checklist according to IEC870-5-101 Interopetability.
The protocol checklist for IEC..101 defines the protocol functions for the TCB interfaces
concerning the RTUs directly connected via conventional telecontrol links.
The checklist for IEC..-101 is included here also because the basic communication
procedures (General Interrogation, Command Transmission etc.) are the same for both
protocol stacks IEC..-101 and IEC..-104.

IEC-60870-5-101
______________________________________________________________________
Companion standard for basic telecontrol tasks
A1 - 1 Interoperability
The companion standard defined above presents sets of parameters and alternatives from which
subsets have to be selected to implement particular telecontrol systems. Certain parameter
values, such as the number of octets in the COMMON ADDRESS of ASDUs represent mutually
exclusive alternatives. This means that only one value of the defined parameters is admitted per
system. Other parameters, such as the listed set of different process information in command and
in monitor direction allow the specification of the complete set or subsets, as appropriate for given
applications. This clause summarizes the parameters of the previous clauses to facilitate a
suitable selection for a specific application. If a system is composed of equipment from different
manufacturers it is necessary that all partners agree on the selected parameters.
The selected parameters should be crossed in the white boxes.
Note: In addition, the full specification of a system may require individual selection of certain
parameters for certain parts of the system, such as the individual selection of scaling factors for
individually addressable measured values.
Note:
Functions which are not (yet) implemented in Siemens Spectrum System do not have the
check box " ". Further investigations are needed if they are required. Mandatory items are
marked by " ".
Parameters which are in addition or different to the TCS 101 are written in italic.
A1 - 1.1 Network Configuration

Configuration

Remark

Multiple Point-to Point

redundant communication links? (y / n / some)

Multipoint-Partyline

Ditto

Multipoint-Star

Ditto

A1 - 1.2 Physical Layer


Transmission Speed (common for both directions)

Circuit V.24 / V.28 (RS 232)


Speed

Circuit X.24/X.27 (RS485) / applicable only for TCI

Remark

Speed

100 bit/s

Remark

4 800 bit/s

200 bit/s

300 bit/s

19 200 bit/s

600 bit/s

38 400 bit/s

1 200 bit/s

56 000 bit/s

2 400 bit/s

64 000 bit/s

9 600 bit/s

applicable only for TCI

IEC-60870-5-101
______________________________________________________________________
A1 - 1.3 Link Layer
Frame format FT 1.2, single character1(=E5) and the fixed time out interval are used exclusively
in this companion standard.
Link transmission procedure
Procedure

Remark

Balanced Transmission
Send / No reply in monitoring direction

only for balanced transmission relevant

Unbalanced Transmission
Number of Data Class 1 requests__
Number of Data Class 2 requests__

default: 2
default: 4
(only for unbalanced transmission relevant)

max. length of the message 116


(number of octets)

default: 255

Number of repeats_____

default: 2

Address field of the link


Description

Remark

not present

only for balanced transmission

1 Octet

2 Octets
structured

only relevant if 2 octets are used

unstructured

A1 - 1.4 Application Layer


Transmission Mode for Application Data
Mode 1 (least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively
in this standard.
Common Address of ASDU
Description

Remark

1 Octet

2 Octets
structured
unstructured

only relevant if 2 octets are used

IEC-60870-5-101
______________________________________________________________________
Information Object Address
Description

Remark

1 Octet
2 Octets

3 Octets

structured

Example for structured addressing scheme:


1st octet: Feeder Number (1 ... 255) 2nd octet: Info
Group (1 ... 255) 3rd octet: Info No. (1 ... 255)

unstructured

Cause of Transmission
1 Octet
2 Octets

2nd octet is used as "Originator Address"

Test bit
Test bit is not evaluated in the Spectrum System

Selection of Standard ASDUs


Process Information in Monitor Direction
Type
Ident

ASDU

Description

Remark

<1>

M_SP_NA_1

Single-point information

<2>

M_SP_TA_1

Single-point information
with time tag

<3>

M_DP_NA_1

Double-point
information

<4>

M_DP_TA_1

Double-point
information with time tag

<5>

M_ST_NA_1

Step position
information

<6>

M_ST_TA_1

Step position
information with time tag

<7>

M_BO_NA_1

Bitstring of 32 bit

<8>

M_BO_TA_1

Bitstring of 32 bit with


time tag

<9>

M_ME_NA_1

Measured value,
normalized value

recommended type

<10>

M_ME_TA_1

Measured value,
normalized value with
time tag

time tag is evaluated by Spectrum only


in case of limit violation

<11>

M_ME_NB_1

Measured value, scaled

IEC-60870-5-101
______________________________________________________________________
value
<12>

M_ME_TB_1

Measured value, scaled


value with time tag

<13>

M_ME_NC_1

Measured value, short


floating point value

<14>

M_ME_TC_1

Measured value, short


floating point value with
time tag

<15>

M_IT_NA_1

Integrated totals

<16>

M_IT_TA_1

Integrated totals with


time tag

<17>

M_EP_TA_1

Event of protection
equipment with time tag

( )

<18>

M_EP_TB_1

Packed start events of


protection equipment
with time tag

on request

( )

<19>

M_EP_TC_1

Packed output circuit


information of protection
equipment with time tag

on request

<20>

M_PS_NA_1

Packed single-point
information with status
change detection

<21>

M_ME_ND_1

Measured value,
normalized value
without quality
descriptor

see Remark of TI <10>

see Remark of TI <10>

transmitted time tag is discardedby


Spectrum

<30> := Single-point information with time tag CP56Time2a

M_SP_TB_1

<31> := Double-point information with time tag CP56Time2a

M_DP_TB_1

<32> := Step position information with time tag CP56Time2a

M_ST_TB_1

<33> := Bitstring of 32 bit with time tag CP56Time2a

M_BO_TB_1

<34> := Measured value, normalized value with time tag CP56Time2a

M_ME_TD_1

<35> := Measured value, scaled value with time tag CP56Time2a

M_ME_TE_1

<36> := Measured value, short floating point value with time tag CP56Time2a

M_ME_TF_1

<37> := Integrated totals with time tag CP56Time2a

M_IT_TB_1

<38> := Event of protection equipment with time tag CP56Time2a

M_EP_TD_1

<39> := Packed start events of protection equipment with time tag CP56Time2a

M_EP_TE_1

<40> := Packed output circuit information of protection equipment with


time tag CP56Time2a

M_EP_TF_1

IEC-60870-5-101
______________________________________________________________________
Cause of Transmission
CoT

Cause

Remark

<1>

periodic, cyclic

Only used for cyclic measured values without time tag.

<2>

background scan

<3>

spontaneous

<5>

requested

<7>

activation confirmation

<9>

deactivation
confirmation

<10>

activation termination

<11>

return information
caused by a remote
command

<12>

return information
caused by a local
command

<20>

interrogated by general
interrogation

Quality Descriptors Evaluated by the SPECTRUM System


QoI

Description

Remark

<NT

not topical

applicable for all information

<IV>

invalid

for measured values, integrated totals

<OV>

overflow

for measured values, tap changer positionstreated as


"invalid"

<SB>

substituted

applicable for all information

<BL>

blocked

applicable for all information

Remark:
Invalid time tags are passed-on from process interface to the Communicator without change.

IEC-60870-5-101
______________________________________________________________________
Process information in control direction
Type
Ident

ASDU

Description

<45>

C_SC_NA_1

Single command

<46>

C_DC_NA_1

Double command

<47>

C_RC_NA_1

Regulating step command

<48>

C_SE_NA_1

Set point command,


normalized value

<49>

C_SE_NB_1

Set point command, scaled


value

<50>

C_SE_NC_1

Set point command, short


floating point value

<51>

C_BO_NA_1

Bitstring of 32 bits

Remark

System Information in Monitoring Direction

<70>

M_EI_NA_1

End of initialization

COI parameters are not evaluated

System Information in Control Direction


Type
Ident

ASDU

Description

Remark

<100>

C_IC_NA_1

Interrogation command

<101>

C_CI_NA_1

Counter interrogation
command

not supported
not supported

<102>

C_RD_NA_1

Read command

<103>

C_CS_NA_1

Clock synchronization
command

<104>

C_TS_NA_1

Test command

not supported

<105>

C_RP_NA_1

Reset process command

not supported

IEC-60870-5-101
______________________________________________________________________
Parameter in Control Direction
Type
Ident

ASDU

Description

Remark

( )

<110>

P_ME_NA_P
q KPA=1
KPA=2
KPA=3/4

Parameter of measured
value, normalized value
- threshold - smoothing
factor - low / high limit

on request

( )

<111>

P_ME_NB_1
KPA=1
KPA=2
KPA=3/4

Parameter of measured
value, scaled value
- threshold - smoothing
factor - low / high limit

ditto

( )

<112>

P_ME_NC_1

Parameter of measured
value, short floating point
value
- threshold - smoothing
factor - low / high limit

ditto

Parameter activation
- act / deact of cyclic
transmission

not supported

KPA=1
KPA=2
KPA=3/4
<113>

P_AC_NA_1
QPA=3

File Transfer in Monitoring Direction


File Transfer in Control Direction
File Transfer
Type
Ident

ASDU

Description

<120>

F_FR_NA_1

File ready

<121>

F_SR_AN_1

Section ready

<122>

F_SC_NA_1

Call directory, select file, call


file, call selection

<123>

F_LS_NA_1

Last section

<124>

F_AF_NA_1

Ack file, ack section

<125>

F_SG_NA_1

Segment

<126>

F_DR_TA_1

Directory

Remark

not implemented

Note:
Source or destination of the file transfer is a directory of the process controlling DAS server.
Preparation or evaluation of the file contents on any other Spectrum server is subject of extra
effort.

IEC-60870-5-101
______________________________________________________________________
A1 - 1.5 Basic Application Functions
General Interrogation
Type
Ident

ASDU

Description

Remark

<100>

C_IC_NA_1
(QOI=20)

global G I

the following COT parameters are applied:


in control direction:
<6> activation (C_IC ACT)in monitoring
direction:<7> activation confirmation (C_IC
ACTCON)
<10> activation termination (C_IC ACTTERM)

<100>

C_IC_NA_1
(QOI=21)

group 1

not supported

<100>

C_IC_NA_1
(QOI=22)

group 2

ditto

etc.

group 3

ditto

group 4

ditto

group 5

ditto

group 6 ...
16

ditto

ditto

Addresses per group have to be defined


Command Transmission
Description

Remark

Direct command transmission


Direct set-point command transmission
Command termination

not supported

Select and execute command

(SCADA function in 3.x)

Select and execute set-point command

(SCADA function in 3.x)

C_SE ACTTERM used

arbitrary

Qualifier for Command Transmission

QOC

Description

Remark

<0>

no additional definition

individual command output pulses are to be


parameterized in the RTU

<1>

Short pulse duration (duration


determined by a system parameter in
the outstation)

<2>

Long pulse duration(duration


determined by a system parameter in
the outstation)

<3>

Persistent output

not supported

IEC-60870-5-101
______________________________________________________________________
(others to be defined)

IEC-60870-5-101
______________________________________________________________________
Counter Interrogation Commands
Type
Ident

ASDU

Description

Remark

<101>

C_CI_NA_1.
..(FRZ=0)

no freeze or reset

not supported

...(FRZ=1)

counter freeze without reset

ditto

...(FRZ=2)

counter freeze with reset

ditto

...(FRZ=3)

counter reset

ditto

...(RQT=0)

no counter request

ditto

...(RQT=1)

request counter group 1

ditto

...(RQT=2)

request counter group 2

ditto

...(RQT=3)

request counter group 3

ditto

...(RQT=4)

request counter group 4

ditto

...(RQT=5)

general request counter

ditto

Note:
all counter commands (freeze, reset) are to be carried out by the RTU. The transmission of the
counter messages is initialized by the RTU spontaneously after each freezing.

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Anexo para IEC870-5-104 (Conexin RTU)

Anexo A_Perfil
IEC104.pdf

Especificaciones de conexin al SITR del CDEC-SIC

17 de 19

TIME-OUTs PARA IEC870-5-104


Definicin de Time-outs
Parmetro

Valor por
Defecto

to

30 s

t1

15 s

t2

10 s

t3

30 s

Notas

Valor
Adoptado

Time-out de establecimiento de
conexin
Time-out de APDU del tipo send o
test
Time-out para confirmaciones en caso
de mensajes sin datos t2 < t1
Time-out para envo de tramas de tipo
S en caso de periodos largos de
inactividad t3 > t1

60 s
15 s
10 s
30 s

Rango de valores para todos los time-outs es de: 1 a 255 s, con una precisin de 1 s.
Nmero mximo de APDU tipo I y ltima confirmacin
Parmetro

Valor por
Defecto

12 APDUs

8 APDUs

Notas

Valor
Adoptado

Mxima diferencia entre nmeros de


secuencia para enviar una variable de
estado.
ltimo reconocimiento despus de recibir
w APDUs del tipo I

12
8

El rango de valores para k: 1 hasta 32767 (215 - 1) APDUs. Precisin de 1 APDU.


El rango de valores para w: 1 hasta 32767 APDUs. Precisin de 1 APDU (Se recomienda que
w no exceda de 2/3 de k)
Nmero de puerto
Parmetro
puerto

Valor por
Defecto
2404

Notas
En todos los casos

RFC 2200 suite


RFC 2200 es un estndar oficial de Internet que describe el estado de estandarizacin de los
protocolos utilizados en internet como se dictamina por the Internet architecture board
(IAB). Ofrece un amplio espectro de estndares utilizados en internet. La seleccin ms
adecuada de documentos de RFC2200 definidos en este estndar para el proyecto debe se
elegida por el usuario de este estndar.
X

Ethernet 802.3
Otras selecciones de RFC2200
Lista de documentos vlidos de RFC2200
1.- ______________________________
2.- ______________________________
3.- ______________________________
4.- ______________________________

CAUSAS DE TRANSMISIN RTU PROTOCOLO IEC870-5-104


Los mensajes de la siguiente tabla corresponden a mensajes con informacin de proceso y
viajan desde una unidad remota hacia el centro de control. Estos mensajes NO tienen
confirmacin a nivel de aplicacin.
Tipo

Significado

Nemotcnico

<1>
<3>

Estado digital simple sin marca de tiempo


Estado digital doble sin marca de tiempo

M_SP_NA_1
M_DP_NA_1

<5>

Posicin de paso

M_ST_NA_1

<11>

Medida analgica, valor escalado

M_ME_NB_1

<15>
<30>
<31>

Totales integrados
Estado digital simple con marca de tiempo extendida
Estado digital doble con marca de tiempo extendida

M_IT_NA_1
M_SP_TB_1
M_DP_TB_1

Causa de Transmisin
<20>
<20>
<3>
<20>
<3>
<20>
<3>
<3>
<3>

General Interrogation
General Interrogation
Spontaneous
General Interrogation
Spontaneous
General Interrogation
Spontaneous
Spontaneous
Spontaneous

Los mensajes de la siguiente tabla corresponden a mensajes con informacin de proceso y


viajan desde el centro de control hacia una unidad remota. Estos mensajes SI tienen
confirmacin a nivel de aplicacin. Es decir, la unidad remota los refleja cambiando nicamente
el primer byte del campo causa de transmisin.
Tipo

Significado

Nemotcnico

<45>

Comando simple

C_SC_NA_1

<46>

Comando doble

C_DC_NA_1

<47>

Comando de posicin de paso

C_RC_NA_1

<49>

Comando de consigna, valor escalado

C_SE_NB_1

Causa de Transmisin
<6> Activation
<8> Deactivation
<7> Activation Confirmation
<9> Deactivation Confirmation
<10> Activation Termination
<6> Activation
<8> Deactivation
<7> Activation Confirmation
<9> Deactivation Confirmation
<10> Activation Termination
<6> Activation
<8> Deactivation
<7> Activation Confirmation
<9> Deactivation Confirmation
<10> Activation Termination
<6> Activation
<8> Deactivation
<7> Activation Confirmation
<9> Deactivation Confirmation
<10> Activation Termination

Los mensajes de la siguiente tabla corresponden a mensajes con informacin de sistema y


viajan desde el centro de control hacia la unidad remota. Estos mensajes SI tienen
confirmacin a nivel de aplicacin. Es decir, la unidad remota los refleja cambiando nicamente
el primer byte del campo causa de transmisin
Tipo
<100>

Significado
Comando de interrogacin

Nemotcnico
C_IC_NA_1

Causa de Transmisin
<6> Activation
<8> Deactivation
<7> Activation Confirmation
<9> Deactivation
Confirmation
<10> Activation Termination

CDEC-SIC
Direccin de Operacin

Mayo de 2007

Perfil DNP 3.0 TCP-IP/Serial:

Perfil DNP3.pdf

Especificaciones de conexin al SITR del CDEC-SIC

18 de 19

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

,QWHURSHUDELOLW\/LVW'13IRU/HYHO
The companion standard defined presents sets of parameters and alternatives from which subsets have to be selected to implement particular telecontrol systems. Certain parameter values, such as the number of octets in the
COMMON ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only one value of the
defined parameters is admitted per system. Other parameters, such as the listed set of different process information in command and in monitor direction allow the specification of the complete set or subsets, as appropriate for
given applications. This clause summarizes the parameters of the previous clauses to facilitate a suitable selection
for a specific application. If a system is composed of equipment stemming from different manufacturers it is necessary that all partners agree on the selected parameters.

Copyright Siemens AG 2000. All Rights Reserved.

DNP restrictions that will be applied are as follows:


a. Redundancy: Master operates in a shared-redundancy mode.
If line is assigned to the primary channel, then no check is made of the secondary (back-up) channel
For RTUs connected by a single transmission line, this redundancy approach is like moving the line from one
front-end processor to another.
At this time, for RTUs connected by independent communications lines (dual ported RTUs), the back-up line
is not used until the primary front-end processor fails over to the secondary.
b. All RTUs will be configured independently by an off-line process. Siemens does not write configuration data
(i.e. association of hardware to software) to RTUs at system start-up time. However, assignment of certain
categories of event data to data classes (i.e. digital events to Class 1, analog to Class 2, etc.) *is* supported.
c.

European projects have used a scheme called Double Channels. This method of redundancy is not supported.

d. Broadcast commands are not supported.


e. All measurement values are mapped to a 16 bit value with a range from 215-1 to -215.
f.

The TCI supports no nodes with the DNP 3.00 implementation.

The selected parameters should be crossed in the white boxes.


In addition, the full specification of a system may require individual selection of certain parameters for certain parts
of the system, such as the individual selection of scaling factors for individually addressed measured values.

1RWH
7KHFKHFNER[HV\RXZLOOILQGEHORZKDYHWKHIROORZLQJPHDQLQJ
q

LPSOHPHQWHGE\6LHPHQV7HOHFRQWURO,QWHUIDFH

n/i

QRWLPSOHPHQWHGE\6LHPHQV7HOHFRQWURO,QWHUIDFH

VXEVHWVHOHFWHGIRUWKLVSURMHFW HPSW\FKHFNER[WREHUHSODFHGE\WKLVV\PERO

PDQGDWRU\

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-1

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

1HWZRUN&RQILJXUDWLRQ
&RQILJXUDWLRQ
Point-to Point

Multiple Point-to Point

Multipoint-Partyline

Multipoint-Star

redundant communication links (yes | no)


redundant communication links (yes | no)
redundant communication links (yes | no)

Copyright Siemens AG 2000. All Rights Reserved.

5HPDUN

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-2

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

3K\VLFDO/D\HU

7UDQVPLVVLRQ6SHHG FRPPRQIRUERWKGLUHFWLRQV
Unbalanced Interchange
Circuit V.24 / V.28 Standard

Copyright Siemens AG 2000. All Rights Reserved.

6SHHG

5HPDUN



6SHHG

5HPDUN

n/i

100 bit/s

4 800 bit/s

n/i

200 bit/s

9 600 bit/s

n/i

300 bit/s

19 200 bit/s

n/i

600 bit/s

n/i

38 400 bit/s

TCB Version 2 (X.27) required

1 200 bit/s

n/i

56 000 bit/s

ditto

2 400 bit/s

n/i

64 000 bit/s

ditto

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-3

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

'DWD/LQN/D\HU

The data link layer uses a standard variable length frame format as defined in the IEC 870-5-1 Transmission
Frame Formats document. The FT3 frame format class is well suited for data transmission between stations that
require medium information transfer rates and low residual error probability.

Copyright Siemens AG 2000. All Rights Reserved.

3URFHGXUH

5HPDUN

Maximum Data Link Frame Size (octets):


Transmitted:
255 + Header (292)
Received:
(must be 292)

Maximum Data Link Re-tries:


Configurable, range 0 to 255

n/i

Unsolicited Responses

3.1

Unsolicited Responses are not supported

Function code Field Values of Control octet Sent from the primary station (PRM=1)
)XQFWLRQ )UDPH7\SH
&RGH

6HUYLFH)XQFWLRQ

)&9
%LW

SEND - CONFIRM expected

Reset of remote link

SEND - CONFIRM expected

Reset of user link

SEND - CONFIRM expected

Test function for link

SEND - CONFIRM expected

User data

SEND - NO REPLAY expected

Unconfirmed user data

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

Request link status

n/i

10

Not used

n/i

11

Not used

n/i

12

Not used

n/i

13

Not used

n/i

14

Not used

n/i

15

Not used

REQUEST - RESOPNSE expected

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-4

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

3.2

Function code Field Values of Control octet Sent from the secondary station (PRM=0)

Copyright Siemens AG 2000. All Rights Reserved.

)XQFWLRQ )UDPH7\SH
&RGH

6HUYLFH)XQFWLRQ

CONFIRM

Ack - positive acknowledgment

CONFIRM

NACK - MEssage not accepted, Link busy

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

n/i

Not used

n/i

10

Not used

11

n/i

12

Not used

n/i

13

Not used

14

Link service not functioning

15

Link service not used or implemented

RESPOND

F-DA02-E-1.3.0.0

Status of Link (DCF = 0 or DFC = 1)

Version 1.3.0.0, 09/00

-5

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,


4.1

7UDQVSRUW/D\HU
Fragmentation for transport frames in receive direction
3URFHGXUH

5HPDUN

Fragmented transport frames


Maximum frame size:
1300 octets

Fragmented transport frames will be supported only in


receive direction.

Maximum transport fragment size:

Copyright Siemens AG 2000. All Rights Reserved.

4.2

n/i

Maximum data link data count


Data link header data count
Transport header
Application Header

+255
-5
-1
=249

octets
octets
octet
octets

Fragmentation for transport frames in transmit direction


3URFHGXUH

5HPDUN

Fragmented transport frames

Fragmented transport frames will not be supported in


transmit direction.

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-6

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,


5.1

Copyright Siemens AG 2000. All Rights Reserved.

5.2

n/i

5.3

$SSOLFDWLRQ/D\HU
Fragmentation for application frames in receive direction
3URFHGXUH

5HPDUN

Fragmented application frames


Maximum frame size:
1300 octets

Fragmented application frames will be supported only


in receive direction.

Fragmentation for application frames in transmit direction


3URFHGXUH

5HPDUN

Fragmented application frames

Fragmented application frames will not be supported


in transmit direction.
FIR and FIN bits are always set to 1.

Function codes
&RGH

)XQFWLRQ

7UDQVIHU)XQFWLRQ&RGHV
q

Confirm

Read

Write

&RQWURO)XQFWLRQ&RGHV
q

Select

Operate

Direct Operate

n/i

Direct Operate - No Acknowledgment

)UHH]H)XQFWLRQ&RGHV
q

Immediate Freeze

Immediate Freeze - No Acknowledgment

7UDQVIHU)XQFWLRQ&RGHV
n/i

Freeze and Clear

n/i

10

Freeze and Clear - No Acknowledgment

n/i

11

Freeze and Time

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-7

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

&RGH
n/i

12

)XQFWLRQ
Freeze and Time - No Acknowledgment

$SSOLFDWLRQ)XQFWLRQ&RGHV
n/i

13

Cold Restart

n/i

14

Warm Restart

n/i

15

Initialize Data to Default

n/i

16

Initialize Application

n/i

17

Start Application

n/i

18

Stop Application

Copyright Siemens AG 2000. All Rights Reserved.

&RQILJXUDWLRQ)XQFWLRQ&RGHV
n/i

19

Save Configuration

n/i

20

Enable Unsolicited Messages

n/i

21

Disable Unsolicited Messages

n/i

22

Assign Class

7LPH6\QFKURQL]DWLRQ)XQFWLRQ&RGHV
q

23

Delay Measurement

5HVHUYH
n/i

24 - 120 Reserved for future use

n/i

121 -128 Reserved for testing only

5HVSRQVH)XQFWLRQ&RGHV
q

129

Response

n/i

130

Unsolicited Messages

F-DA02-E-1.3.0.0

Confirm

Version 1.3.0.0, 09/00

-8

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

'DWD2EMHFWVDQG)XQFWLRQV

Copyright Siemens AG 2000. All Rights Reserved.

2EMHFW *URXS9DULDWLRQ

5HTXHVW)XQFWLRQ

4XDOLILHU D

5HVSRQVH
)XQFWLRQ

4XDOLILHUD

Single-Bit Binary Input (1,1)

Read

01, 06

Response

n/i

Single-Bit Binary Input (1,1)

Assign Class

01, 06

Response

Binary Input with Status (1,2)

Read

01, 06

Response

Binary Input Change Without Time


Read
(2,1)

01, 06

Response

n/i

Binary Input Change Without Time


Assign Class
(2,1)

01, 06

Response

Binary Input Change With Time


(2,2)

Read

01, 06

Response

n/i

Binary Input Change With Time


(2,2)

Assign Class

01, 06

Response

Binary Input Change With Relative


Read
Time (2,3)

01, 06

Response

n/i

Binary Input Change With Relative


Assign Class
Time (2,3)

01, 06

Response

Binary Output Status 10,2)

Read

01, 06

Response

n/i

Binary Output Status (10,2)

Assign Class

01, 06

Response

Control Relay Output Block (12,1)

Select, Operate,
Direct Operate

28

Response

Echoes
Request

n/i

Pattern Control Block (12,2)

n/i

Pattern Mask (12,3)

32-Bit Binary Counter (20,1)

Read

01, 06

Response

16-Bit Binary Counter (20,2)

Read

01, 06

Response

32-Bit Delta Counter (20,3)

Read

01, 06

Response

16-Bit Delta Counter (20,4)

Read

01, 06

Response

32-Bit Binary Counter Without


Flag (20,5)

Read

01, 06

Response

16-Bit Binary Counter Without


Flag (20,6)

Read

01, 06

Response

32-Bit Delta Counter Without Flag


Read
(20,7)

01, 06

Response

16-Bit Delta Counter Without Flag


Read
(20,8)

01, 06

Response

32-Bit Frozen Counter (21,1)

Read

01, 06

Response

16-Bit Frozen Counter (21,2)

Read

01, 06

Response

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

-9

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

Copyright Siemens AG 2000. All Rights Reserved.

2EMHFW *URXS9DULDWLRQ

5HTXHVW)XQFWLRQ

4XDOLILHUD

5HVSRQVH
)XQFWLRQ

4XDOLILHUD

32-Bit Frozen Delta Counter


(21,3)

Read

01, 06

Response

16-Bit Frozen Delta Counter


(21,4)

Read

01, 06

Response

32-Bit Frozen Counter Without


Flag (21,9)

Read

01, 06

Response

16-Bit Frozen Counter Without


Flag (21,10)

Read

01, 06

Response

32-Bit Frozen Delta Counter WithRead


out Flag (21,11)

01, 06

Response

16-Bit Frozen Delta Counter WithRead


out Flag (21,12)

01, 06

Response

32-Bit Counter Change Event


Without Time (22,1)

Read

01, 06

Response

16-Bit Counter Change Event


Without Time (22,2)

Read

01, 06

Response

32-Bit Delta Counter Change


Event Without Time (22,3)

Read

01, 06

Response

16-Bit Delta Counter Change


Event Without Time (22,4)

Read

01, 06

Response

32-Bit Counter Change Event


With Time (22,5)

Read

01, 06

Response

16-Bit Counter Change Event


With Time (22,6)

Read

01, 06

Response

32-Bit Delta Counter Change


Event With Time (22,7)

Read

01, 06

Response

16-Bit Delta Counter Change


Event With Time (22,8)

Read

01, 06

Response

32-Bit Frozen Counter Event WithRead


out Time (23,1)

01, 06

Response

16-Bit Frozen Counter Event WithRead


out Time (23,2)

01, 06

Response

32-Bit Frozen Delta Counter Event


Read
Without Time (23,3)

01, 06

Response

16-Bit Frozen Delta Counter Event


Read
Without Time (23,4)

01, 06

Response

32-Bit Frozen Counter Event With


Read
Time (23,5)

01, 06

Response

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

- 10

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

Copyright Siemens AG 2000. All Rights Reserved.

2EMHFW *URXS9DULDWLRQ

4XDOLILHUD

5HTXHVW)XQFWLRQ

5HVSRQVH
)XQFWLRQ

4XDOLILHUD

16-Bit Frozen Counter Change


With Time (23,6)

Read

01, 06

Response

32-Bit Frozen Delta Counter Event


Read
With Time (23,7)

01, 06

Response

16-Bit Frozen Delta Counter Event


Read
With Time (23,8)

01, 06

Response

32-Bit Analog Input (30,1)

Read

01, 06

Response

16-Bit Analog Input (30,2)

Read

01, 06

Response

32-Bit Analog Input Without Flag


Read
(30,3)

01, 06

Response

16-Bit Analog Input Without Flag


Read
(30,4)

01, 06

Response

32-bit Analog Change Event WithRead, Assign Class 06


out Time (32,1)

Response

16-bit Analog Change Event WithRead, Assign Class 06


out Time (32,2)

Response

32-bit Analog Change Event With


Read, Assign Class 06
Time (32,3)

Response

16-bit Analog Change Event With


Read, Assign Class 06
Time (32,4)

Response

32-Bit Analog Output (41,1)

Select, Operate,
Direct Operate

28

Response

Echoes
Response

16-Bit Analog Output (41,2)

Select, Operate,
Direct Operate

28

Response

Echoes
Response

Time and Data (50,1)

Write

07

Response

n/i

Time and Data with Interval (50,2)

Time and Data CTO (51,1)

Read

Response

Unsynchronized Time and Data


CTO (51,2)

Read

Response

n/i

Time Delay Coarse Information


(52,1)

Time Delay Fine (52,2)

Delay Measurement 07

Response

07

Class Zero Data (60,1)

Read

Response

Class One Data (60,2)

Read, Assign Class 06, 08

Response

Class Two Data (60,3)

Read, Assign Class 06, 08

Response

Class Three Data (60,4)

Read, Assign Class 06, 08

Response

n/i

File Identifier (70,1)

F-DA02-E-1.3.0.0

06

Version 1.3.0.0, 09/00

- 11

6,1$876SHFWUXP
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
7HOHFRQWURO,QWHUIDFH7&,

Copyright Siemens AG 2000. All Rights Reserved.

2EMHFW *URXS9DULDWLRQ
q

Internal Indications (80,1)

n/i

Storage Object (81,1)

n/i

Device Profile (82,1)

n/i

Private Registration Object (83,1)

n/i

Private Registration Object


Descriptor (83,2)

n/i

Application Identifier (90,1)

n/i

Short Floating Point (100,1)

n/i

Long Floating Point (100,2)

n/i

Extended Floating Point (100,3)

n/i

Small Packed Binary-Coded Decimal (101,1)

n/i

Medium Packed Binary-Coded


Decimal (101,2)

n/i

Large Packed Binary-Coded Decimal (101,3)

5HTXHVW)XQFWLRQ
Write

4XDOLILHUD
00

5HVSRQVH
)XQFWLRQ
Response

4XDOLILHUD
00

;LQGLFDWHVWKDWWKHTXDOLILHUFRGHV LQ+H[ IRUWKHPDUNHGREMHFWVDUHVXSSRUWHGIRUDOOW\SHV


RIUHVSRQVHGDWD

F-DA02-E-1.3.0.0

Version 1.3.0.0, 09/00

- 12

CDEC-SIC
Direccin de Operacin

ANEXO 5

Mayo de 2007

PROTOCOLOS IEC 870-5-101 Y DNP3.0 SERIAL: DISPOSITIVO


DERIVADOR

ModemShare
Devices 56606668[1]

Especificaciones de conexin al SITR del CDEC-SIC

19 de 19

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 1 of 7

Code Ident. 71682

Specification Control Document

Modem Sharing Device, Active, SMSD3


With Case for Modem Rack Mounting, Screwlock Arrangement #2
Note: See Spec. 56605890 for SMSD with Screwlock Arrangement #1- Panel Mounting
56606660 for SMSD2 with Screwlock Arrangement #2- Modem Mounting

M. Brown
_________________
Originator

M. Brown
____________________
Engineer

_________________
Checked

____________________
Approved

Revision Record
Rev ECO
01

Description
Initial Draft

Appd. Date
08/22/05

_______________________________________________________________________

File (Word): 56606668.doc

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 2 of 7

Code Ident. 71682


Scope
1.1

This specification defines the detail requirements for a Modem Sharing


Device, based on RS232 ports, that incorporates active electronics and that
is port-powered.

1.2

First Used On: OPPD project; also used as a general solution for RS232
line sharing by redundant CFE servers.

1.0

Requirements

2.1

Product Functional Description


The device is a custom Modem Data Splitter for Siemens (designated
SMSD3 by B&B Electronics), otherwise also known as an active Modem
Sharing Device (designated MSD by legacy at Siemens). The device
supports two slave ports and one master port for RS232 signals. Each
slave port supports three input signals: TD, RTS, and DTR. Internal
circuitry for these three input signals on the slave ports provides active
RS232 chips in the circuit. The RS232 receiver chips tie into an AND
gate and then out to an RS232 driver on the master port. In this way, it is
guaranteed that when one slave port shuts down, it does not affect the
other slave ports data communications. The MSD is port-powered. (The
supplier must design the device with the goal of minimizing internal
power consumption so that the viability of port-powering is maximized.)
Dual RJ11-4 pin female connectors, connected in parallel, are also
included for optional 12vdc for applications in which port powering does
not work (as specified by supplier). All of the signal lines coming in from
the master port get passed directly to both slave ports. The MSD features
one male DB25 pin connector on the master port. The two slave ports
feature RJ45-10 pin female connectors. The MSD is packaged in an
enclosure for one DB25 pin connector and two RJ45 connectors. Overall
dimensions of the enclosure will be 3.95"L x 2.3"H x 0.7"W. The unit
defined in this document differs from two earlier versions (B&B
Electronics SMSD and SMSD2). SMSD3 differs from SMSD with
screwlock arrangement and case width. SMSD3 differs from SMSD2 with
a case width of 0.7 inch as shown in diagram 2. The original version
device with screwlock arrangement #1 is detailed in Spec. 56605890. The
second version with screwlock arrangement #2 is detailed in Spec.
56606660.
All three devices (SMSD, SMSD2 & SMSD3) are electrically equivalent.
In general, SMSD3 can replace SMSD2 for most or all applications.

File (Word): 56606668.doc

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 3 of 7

Code Ident. 71682

2.2

Technical Information Required of Supplier

Circuit Schematic.

Mechanical Dimensions Drawing, including all connector locations.

Specification of all conditions for applications that will require


external power (e.g. perhaps minimum voltage levels on hardware
handshaking signals).

2.3

Data Rate: Supports up to 115.2K bps.

2.4

Isolation Type: Non-Isolated

2.5

Surge Suppression Type: None

2.6

Enclosure Dimensions and Material


The device is packaged in an enclosure that provides one DB25 connector
on one end, and two RJ45-10 pin connectors on the other end. In typical
usage, the device is mounted to a modem DB25 connector using standard
jackscrew hardware for the DB25 connector. Overall dimensions of the
enclosure will be 3.95" x 2.3" x 0.7".

2.7

Connectors and Connector Hardware Description: One male DB25


pin connector with standard holes using 2 male screwlocks and two female
RJ45-10 pin connectors. In addition, two RJ11-4 pin jacks for external
power; see description below under Power Supply.

2.8

Power Supply
Port powered and optional external 12vdc powered. The optional external
12vdc power, if used, is connected at an RJ11-4 pin jack. A second RJ114 pin jack is internally connected in parallel with the first RJ11 jack, and
this provides a means to connect external power in a daisy-chain manner
between multiple devices. At each RJ11 jack, 2 adjacent pins on one side
of the connector are used for positive polarity, and the 2 adjacent pins on
the other side of the connector are used for negative polarity.

File (Word): 56606668.doc

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 4 of 7

Code Ident. 71682


2.9

Connector Pin Assignments


See diagram.

2.10

Labeling
Permanently identify the device with the following information:
Siemens part number and revision (from this Document)
Vendor name, code or logo
Vendor part number or model number
Date code of Manufacture
Labeling method and format must be approved by the Siemens design
control organization via first article inspection. Any later changes by the
supplier to this method must also be approved prior to implementation.

2.11

Testing
The manufacturer must individually test each device. Evidence of
successful testing must be provided either individually or by lot.
Individually stamping the devices, or certificate of testing for a date code
lot, are examples of acceptable test evidence.

2.0

Vendor
See Authorized Vendor List (AVL) for approved vendor and vendor part
number. Do not rely on attached vendor data (if present) or other vendor
references contained in this document.

File (Word): 56606668.doc

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 5 of 7

Code Ident. 71682


______________________________________________________________________
3.0

Tables & Diagrams

TABLE 1: Connector Pin Assignments

Port
Name

Connector
Type

Port A
Port A
Port A
Port A
Port A
Port A
Port A
Port A
Port A
Port A

RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female

Port
Name

Connector
Type

Port B
Port B
Port B
Port B
Port B
Port B
Port B
Port B
Port B
Port B

RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female
RJ45-10 pin-Female

Connector
Designation
J1- 1
J1- 2
J1- 3
J1- 4
J1- 5
J1- 6
J1- 7
J1- 8
J1- 9
J1-10

Connector
Designation
J2- 1
J2- 2
J2- 3
J2- 4
J2- 5
J2- 6
J2- 7
J2- 8
J2- 9
J2-10

Table 1: continued on following sheet.

File (Word): 56606668.doc

RS232
Signal Name
Ring
DSR
RTS-A
Shield
TXD-A
RXD
Signal Gnd
CTS
DTR-A
CD

RS232
Signal Name
Ring
DSR
RTS-B
Shield
TXD-B
RXD
Signal Gnd
CTS
DTR-B
CD

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 6 of 7

Code Ident. 71682


Table 1: Continued

Port
Name
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem
Modem

Connector
Type
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male
DB25-Male

Connector
Designation
J3- 1
J3- 2
J3- 3
J3- 4
J3- 5
J3- 6
J3- 7
J3- 8
J3-20
J3-22

Port
Name

Connector
Type

Ext Power 1
Ext Power 1
Ext Power 1
Ext Power 1

RJ11-4 pin-Female
RJ11-4 pin-Female
RJ11-4 pin-Female
RJ11-4 pin-Female

J4- 1
J4- 2
J4- 3
J4- 4

12 VDC Positive
12 VDC Positive
12 VDC Negative
12 VDC Negative

Ext Power 2
Ext Power 2
Ext Power 2
Ext Power 2

RJ11-4 pin-Female
RJ11-4 pin-Female
RJ11-4 pin-Female
RJ11-4 pin-Female

J5- 1
J5- 2
J5- 3
J5- 4

12 VDC Positive
12 VDC Positive
12 VDC Negative
12 VDC Negative

File (Word): 56606668.doc

Connector
Designation

RS232
Signal Name
Shield
TXD
RXD
RTS
CTS
DSR
Signal Gnd
CD
DTR
Ring

Power
Signal Name

Siemens Power T&D, Inc.


Energy Management & Information Systems

Doc. 56606668
Rev. 01
Page 7 of 7

Code Ident. 71682


____________________________________________________________________
DIAGRAM 1: Mating RJ45 & RJ11 Pin Orientation

Mating
RJ45
10-pin
Plug

Pin
1

Pin
1

Pin
10

Pin
4
Mating
RJ11
4-pin
Plug

Viewed
From
Contact
Side

Viewed
From
Contact
Side

DIAGRAM 2: Connector Locations & Screwlock Arrangement - Modem Rack Mounting

3.95 inch

0.7 in

0.165 inch
(Typical)
Modem
Port

Port A
RJ45-10 pin
Female
J1

Male screwlocks

DB25
Male

Port B
RJ45-10 pin
Female
J2

J3

Pin 1
1.3 inch Approx.
Side View

File (Word): 56606668.doc

J4
Power 1
RJ11-4 pin
Female

J5
Power 2
RJ11-4 pin
Female

End View