Beruflich Dokumente
Kultur Dokumente
DIRECCIN DE OPERACIN
NDICE
1. INTRODUCCIN....................................................................................... 3
2. REQUERIMIENTOS PARA EL REPORTE DE INFORMACIN ........................... 3
2.1. EQUIPOS DE ADQUISICIN DE DATOS...................................................... 3
2.2. ENLACES Y PROTOCOLOS DE COMUNICACIONES ....................................... 3
2.2.1. Protocolo TCP/IP .................................................................................. 3
2.2.2. Protocolo Serial .................................................................................... 4
2.3. 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. PRUEBAS DE PUESTA EN SERVICIO........................................................... 6
2.7.1. Prueba de Enlace:................................................................................. 6
2.7.2. Prueba Inicial: ...................................................................................... 6
2.7.3. Prueba Punto a Punto: .......................................................................... 6
2.8. 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 Mayo de 2007
Direccin de Operacin
1. INTRODUCCIN
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
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 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.
Con esta informacin, Synapsis gestionar los permisos correspondientes para que el
coordinado pueda ingresar al CPD y efectuar sus trabajos.
A nivel de capa de enlace se debe constatar que los equipos comuniquen verificando
rutas y permisos de los sistemas.
Se revisa que todos los cambios de las variables transferidas se procesen en forma
correcta en el SCADA del CDEC-SIC.
2.8.1. HOSTING
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.
ANEXOS
SCADA CDEC-SIC
CPD Principal:
IP router lado LAN: 10.39.XX.YY
Edo. Frei Montalva 2205, Switch
Comuna Independencia, Santiago Redes Externas
Firewall: 10.39.XX.ZZ
CPD Respaldo: IP(gateway) que resuelve acceso a servidores ICCP
del CDEC-SIC para SCADA del COORDINADO
Santa Rosa 76,
Comuna Santiago, Santiago
Firewall
SCADA
LAN A
LAN B
Notas:
Parmetro Valor
Nombre del sistema SCADA CDEC-SIC ICCP
Nombre del Centro de Control SCADA CDEC-SIC MCS
Nmero Mximo de Transfer Sets 400
Nmero Mximo de Data Sets 400
Tamao Mximo de Mensajes MMS 15000
Bloques MMS soportados 1y2
Nombre del Remoto (mirado desde SCADA CDEC-SIC) COORDINA
Nombre del Centro de Control Remoto (mirado desde SCADA CDEC- RALCO _DOMAIN
SIC)
Iniciador de Requerimiento de Asociacin SCADA CDEC-SIC
Time Out del Requerimiento de Asociacin 18 seg.
Reintento de Requerimiento de Asociacin 8 seg.
Time Out del Reintento de Requerimiento de Asociacin 10 seg.
Versin de la Tabla Bilateral SYNAPSIS
Versin del ICCP 1996-08
Nombre del Dominio Local (mirado desde SCADA CDEC-SIC) DOMAIN_ COORDINA
Nombre del Dominio Remoto (mirado desde SCADA CDEC-SIC) DOMAIN_MCS
Nombre del LINK COORDINA
Nmero del Canal 11
Nombre del AR Local LOCAL_ COORDINA
Nombre del AR Remoto Primario REMOTE_ COORDINA
Nombre del AR Remoto Alternativo
Informacin del grupo de datos reportados por excepcin y con transmisin de la estampa
de tiempo
Parmetro Valor
Nombre del Grupo Excpt_1
Reporte Peridico de Datos No Aplica
Reporte por Excepcin de Datos S
Intervalo de Chequeo de Integridad 600 seg.
Parmetro Valor
Nombre del Grupo Perio_1
Reporte Peridico de Datos S
Reporte por Excepcin de Datos No Aplica
Periodicidad del Reporte de Datos 10 seg.
Begin_Local
Common_Name = LOCAL_COORDINA
AP_Title = 1 2 50 18
AP_InvokeID = 100
AE_Qualifier =2
AE_InvokeID =1
Psel = 00000068
Ssel = 0001
Tsel = 0001
Subnet =0
QOS =0
End_Local
Begin_Remote
Common_Name = REMOTE_ COORDINA
AP_Title = 1 2 50 18
AP_InvokeID = 100
AE_Qualifier =2
AE_InvokeID =1
Psel = 00000068
Ssel = 0001
Tsel = 0001
Subnet =0
QOS =0
IP_ADDRESS = ip servidor ICCP del COORDINADO
Transport = TCP
End_Remote
Nombre UTR: SE Chile / Central Chile Enlace de Comunicacin 128 kbps o superior
Direccin Fsica: AA
Direccin Lgica: BB
SCADA CDEC-SIC
Dispositivo Comunicaciones
Instalaciones CPD Synapsis
Por ejemplo: Mdem
CPD Principal:
RAN1
RAN2
LAN A
LAN B
TCS1
TCS2
Notas:
Perfil
IEC-104-101.pdf
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.
Configuration Remark
Multiple Point-to Point redundant communication links? (y / n / some)
Multipoint-Partyline Ditto
Multipoint-Star Ditto
Frame format FT 1.2, single character1(=E5) and the fixed time out interval are used exclusively
in this companion standard.
Procedure Remark
Balanced Transmission
Send / No reply in monitoring direction only for balanced transmission relevant
Unbalanced Transmission
Number of Data Class 1 requests__ default: 2
Number of Data Class 2 requests__ default: 4
(only for unbalanced transmission relevant)
max. length of the message 116 default: 255
(number of octets)
Number of repeats_____ default: 2
Description Remark
not present only for balanced transmission
1 Octet
2 Octets
structured only relevant if 2 octets are used
unstructured
Mode 1 (least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively
in this standard.
Description Remark
1 Octet
2 Octets
structured only relevant if 2 octets are used
unstructured
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
Test bit
Test bit is not evaluated in the Spectrum System
Cause of Transmission
Remark:
Invalid time tags are passed-on from process interface to the Communicator without change.
IEC-60870-5-101
______________________________________________________________________
File Transfer
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
______________________________________________________________________
General Interrogation
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
(others to be defined)
IEC-60870-5-101
______________________________________________________________________
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 Mayo de 2007
Direccin de Operacin
Anexo A_Perfil
IEC104.pdf
Definicin de Time-outs
Rango de valores para todos los time-outs es de: 1 a 255 s, con una precisin de 1 s.
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
Valor por
Parmetro Notas
Defecto
puerto 2404 En todos los casos
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
1.- ______________________________
2.- ______________________________
3.- ______________________________
4.- ______________________________
CAUSAS DE TRANSMISIN RTU PROTOCOLO IEC870-5-104
Perfil DNP3.pdf
,QWHURSHUDELOLW\/LVW'13IRU/HYHO
The companion standard defined presents sets of parameters and alternatives from which subsets have to be se-
lected 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 informa-
tion 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 nec-
essary that all partners agree on the selected parameters.
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
Copyright Siemens AG 2000. All Rights Reserved.
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 support-
ed.
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
x VXEVHWVHOHFWHGIRUWKLVSURMHFWHPSW\FKHFNER[WREHUHSODFHGE\WKLVV\PERO
n PDQGDWRU\
1HWZRUN&RQILJXUDWLRQ
&RQILJXUDWLRQ 5HPDUN
redundant communication links (yes | no)
q Point-to Point
3K\VLFDO/D\HU
7UDQVPLVVLRQ6SHHGFRPPRQIRUERWKGLUHFWLRQV
Unbalanced Interchange
Circuit V.24 / V.28 Standard
'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.
3URFHGXUH 5HPDUN
Maximum Data Link Frame Size (octets):
q Transmitted: 255 + Header (292)
Received: (must be 292)
Maximum Data Link Re-tries:
q
Configurable, range 0 to 255
n/i Unsolicited Responses Unsolicited Responses are not supported
Copyright Siemens AG 2000. All Rights Reserved.
3.1 Function code Field Values of Control octet Sent from the primary station (PRM=1)
3.2 Function code Field Values of Control octet Sent from the secondary station (PRM=0)
7UDQVSRUW/D\HU
3URFHGXUH 5HPDUN
Fragmented transport frames Fragmented transport frames will be supported only in
q
Maximum frame size: 1300 octets receive direction.
Maximum transport fragment size:
3URFHGXUH 5HPDUN
Fragmented transport frames will not be supported in
n/i Fragmented transport frames
transmit direction.
$SSOLFDWLRQ/D\HU
3URFHGXUH 5HPDUN
Fragmented application frames Fragmented application frames will be supported only
q
Maximum frame size: 1300 octets in receive direction.
3URFHGXUH 5HPDUN
Fragmented application frames will not be supported
Copyright Siemens AG 2000. All Rights Reserved.
&RGH )XQFWLRQ
7UDQVIHU)XQFWLRQ&RGHV
q 0 Confirm
q 1 Read
q 2 Write
&RQWURO)XQFWLRQ&RGHV
q 3 Select
q 4 Operate
q 5 Direct Operate
n/i 6 Direct Operate - No Acknowledgment
)UHH]H)XQFWLRQ&RGHV
q 7 Immediate Freeze
q 8 Immediate Freeze - No Acknowledgment
7UDQVIHU)XQFWLRQ&RGHV
n/i 9 Freeze and Clear
n/i 10 Freeze and Clear - No Acknowledgment
n/i 11 Freeze and Time
&RGH )XQFWLRQ
n/i 12 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
&RQILJXUDWLRQ)XQFWLRQ&RGHV
n/i 19 Save Configuration
n/i 20 Enable Unsolicited Messages
n/i 21 Disable Unsolicited Messages
Copyright Siemens AG 2000. All Rights Reserved.
'DWD2EMHFWVDQG)XQFWLRQV
5HVSRQVH
2EMHFW*URXS9DULDWLRQ 5HTXHVW)XQFWLRQ 4XDOLILHU D 4XDOLILHUD
)XQFWLRQ
q Single-Bit Binary Input (1,1) Read 01, 06 Response X
n/i Single-Bit Binary Input (1,1) Assign Class 01, 06 Response X
q Binary Input with Status (1,2) Read 01, 06 Response X
Binary Input Change Without Time
q Read 01, 06 Response X
(2,1)
Binary Input Change Without Time
n/i Assign Class 01, 06 Response X
(2,1)
Binary Input Change With Time
q Read 01, 06 Response X
(2,2)
Binary Input Change With Time
n/i Assign Class 01, 06 Response X
(2,2)
Copyright Siemens AG 2000. All Rights Reserved.
5HVSRQVH
2EMHFW*URXS9DULDWLRQ 5HTXHVW)XQFWLRQ 4XDOLILHUD 4XDOLILHUD
)XQFWLRQ
32-Bit Frozen Delta Counter
q Read 01, 06 Response X
(21,3)
16-Bit Frozen Delta Counter
q Read 01, 06 Response X
(21,4)
32-Bit Frozen Counter Without
q Read 01, 06 Response X
Flag (21,9)
16-Bit Frozen Counter Without
q Read 01, 06 Response X
Flag (21,10)
32-Bit Frozen Delta Counter With-
q Read 01, 06 Response X
out Flag (21,11)
16-Bit Frozen Delta Counter With-
q Read 01, 06 Response X
out Flag (21,12)
32-Bit Counter Change Event
q
Copyright Siemens AG 2000. All Rights Reserved.
5HVSRQVH
2EMHFW*URXS9DULDWLRQ 5HTXHVW)XQFWLRQ 4XDOLILHUD 4XDOLILHUD
)XQFWLRQ
16-Bit Frozen Counter Change
q Read 01, 06 Response X
With Time (23,6)
32-Bit Frozen Delta Counter Event
q Read 01, 06 Response X
With Time (23,7)
16-Bit Frozen Delta Counter Event
q Read 01, 06 Response X
With Time (23,8)
q 32-Bit Analog Input (30,1) Read 01, 06 Response X
q 16-Bit Analog Input (30,2) Read 01, 06 Response X
32-Bit Analog Input Without Flag
q Read 01, 06 Response X
(30,3)
16-Bit Analog Input Without Flag
q Read 01, 06 Response X
(30,4)
32-bit Analog Change Event With-
Copyright Siemens AG 2000. All Rights Reserved.
5HVSRQVH
2EMHFW*URXS9DULDWLRQ 5HTXHVW)XQFWLRQ 4XDOLILHUD 4XDOLILHUD
)XQFWLRQ
q Internal Indications (80,1) Write 00 Response 00
n/i Storage Object (81,1)
n/i Device Profile (82,1)
n/i Private Registration Object (83,1)
Private Registration Object
n/i
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)
Small Packed Binary-Coded Deci-
n/i
mal (101,1)
Copyright Siemens AG 2000. All Rights Reserved.
ModemShare
Devices 56606668[1]
Note: See Spec. 56605890 for SMSD with Screwlock Arrangement #1- Panel Mounting
56606660 for SMSD2 with Screwlock Arrangement #2- Modem Mounting
M. Brown M. Brown
_________________ ____________________
Originator Engineer
_________________ ____________________
Checked Approved
Revision Record
Rev ECO Description Appd. Date
01 Initial Draft 08/22/05
_______________________________________________________________________
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
Circuit Schematic.
Port powered and optional external 12vdc powered. The optional external
12vdc power, if used, is connected at an RJ11-4 pin jack. A second RJ11-
4 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.
See diagram.
2.10 Labeling
2.11 Testing
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.
______________________________________________________________________
Table 1: Continued
____________________________________________________________________
Viewed Viewed
From From
Contact Contact
Side Side
Pin 1
1.3 inch Approx. J4 J5 End View
Side View
Power 1 Power 2
RJ11-4 pin RJ11-4 pin
Female Female