9) front end processor
Post on 07-Mar-2016
61 Views
Preview:
DESCRIPTION
TRANSCRIPT
-
PCU 400 Product Presentation
General Models
Embedded Type
-
Functions:
Front-End for SPIDER or SCADA RSP protocol to SPIDER Downline loading of DB from SPIDER 124 multi-drop lines to RTUs Protocol configurable per line Various communication media Redundancy
PCU 400 as Front-End
Applicatio
n
Servers
RSP protocol over
Ethernet or RS-232
NG WT
ZG
1 15
PCU 400
RTU or
SCS system
Available RTU protocols
-
Functions:
Data concentrator Multiple multi-drop lines to RTUs / IEDs Multiple lines to Master systems Protocol configurable per line Media converter Local configuration Allow connection to old systems
PCU 400 as Concentrator for SA and SCADA
NG
WT
ZG
1 15
Configuration Tool
NG
WT
ZG
1 15
Remote Master
Systems
RTU or
Protection relay
F.ex. IEC870-5-101
-
Functions:
Connection of new RTU to old Master System Connection of old RTUs to new Master System One line to RTUs / Protection relays One line to the Master system Media converter (dial-up to leased line) Local configuration
PCU 400 as Converter
NG
WT
ZG
1 15
Remote
Master System
RTU or
SA system
F.ex. IEC870-5-101
F.ex. Indactic 2033
Configuration Tool
-
PCU 400 Host www-server
Logging
Current value
Event list
Device status
The PCU400 also supports web-
interface for some protocols for
remote debugging
-
PCU400 Mainframe
Industrial PC Chassis or Desktop
PCI slot, half or full length
CDRW-device
Intel Pentium 4 compatible CPU
Minimum 256Mb Memory
Redundant Ethernet ports for Dual-LAN
Ethernet port for Communication Modules
Graphic card
Rack-mountable
-
OCC (Octal Communication
Controller) is a device that enables
distribution of serial communication
ports through ethernet based
networks
PCU400 Communication Module(OCC Unit)
8 serial connectors and one ethernet connector 64kbps per channel in parallel Ethernet connection to PCU mainframe DIN Rail mounted DC powered (24V DC)
-
PCU400 Hardware Assembly
HUB
1 2 3 4 5 6 7 8
Ethernet
1 2 3 4 5 6 7 8
Ethernet
1 2 3 4 5 6 7 8
Ethernet
OCC Unit connected to PCU through a hub or switch IP Address assigned to OCC through DHCP protocol
-
PCU400 Line Switch
Line Switch
1 RTU line per unit
Speed up to 115 kbps
Connection to A and B system
Test connector for line analyzer
DIN-mounted
Redundant power input
Galvanic isolated B-side
-
PCU400 Implemented protocols
Slave Protocols Master Protocols Master Protocols contd
IEC 60870-5-101 IEC 60870-5-101 TG709
IEC 60870-5-104 IEC 60870-5-104 TG065
ADLP180 ADLP80 USART
RP570 ADLP180 SINAUT 8 FW (DPDM)
Teleconnect III RP570/571 Indactic 35
DNP 3.0 Indactic 33,33/41A WISP
OPC server Indactic 2033 WISP+
Conitel 300 Teleconnect III
MODBUS RTU Netcon 8830
Field Buses TG800 HNZ
LON DNP 3.0 Teleconnect II
SPA-bus Mobitex ECMA 24
GCOM Siemens ST1 DDE and OPC client
-
PCU400 A
RTU lines
PCU400 B
Main Computer A (Linux)
RCS Application
Rest of SPIDER
Main Computer B (Linux)
RCS Application
Rest of SPIDER
RSP Links
LAN or WAN
PCU 400 Connection to SPIDER
-
PCU400 Distributed Functionality
The Data Acquisition System is distributed
in two software components:
RCS Application residing in SPIDER Supervision of PCU connection via TCP/IP comports
Handling of line switchover
Handling of redundant lines
Interfaces the SCADA application
Communication statistics
Handling of telephone connections and modem pools
Scaling of measurands
RSP Master
Database loading
PCU400 Polling and Protocol translation
Time synchronization
RSP slave
PCU400
RCS Application
-
API/
Queue API/
Queue
Customer data
Data
Engineering
B Module
Avanti Database
Line/Data Supervision
PCU400 MMI
RSP Protocol
RCS Database
SPIDER (SCADA Servers) RCS
Avanti
PCU 400 Data flow - SCADA
Population
Building up an RCS system database is called Avanti Import Database is sent from the RCS Application to each PCU as Parameter Data dump for Point data (PDP) and Parameter Data dump for Line parameters (PDL)
The loading occurs as soon the RCS Application receives a status message (communication link restarted) or if the database version number differs from the corresponding PCU.
-
Secure Data Flow
5
4
LAN 1
LAN 2
Application Server A Application Server B
RCS Application B RCS Application A
1 PCU400 A PCU400 B
Line switch
RTU
1. Redundant PCUs
2. Dual LAN
3. Line Unit, A and B
side
4. Logging between
RCS applications
in a redundant
system
5. Logging between
Application
Servers
Connection if dual LANs
RSP lines
RTU lines
2
3 3
-
PCU Database Objects
Process Communication Unit (PCU) The class defines one PCU and all possible communication paths
available to reach the physical PCU
Communication line (group of physical lines) The class is a set of all possible communication paths available to
reach a physical RTU
Line unit (physical line) The Line unit class represents a single or a redundnat PCU
configuration but only a single communication channel to the RTU
RTU The class defines one RTU. The RTU represents a distributed I/O
device in the system
Scan group Data types (AMV/DMV, IND, CMD, ACC, REG, SPV,
GOM)
-
Com Line and Line Unit Relation
LAN or WAN
Database-Object level
Hardware
level
Line Pool/
Com line
Line Unit 1
Line Unit 2
Line Unit 3
Line Switch
Line Pool 1 = Com line 1
A B
Line Unit 1
A B
Line Unit 2
A B
Line Unit x
Ch 1A Ch 2A Ch xA
PCU 1
Ch 1B Ch 2B Ch xB
PCU 2
Each Line Unit side is connected to a PCU
number
The PCU can be distributed
Each RTU belongs to one Line Pool
Line switch only if redundant PCUs
Line 1, to RTU
Line Switch
Line 2, to RTU
-
PCU400
SW bus (RSP)
RCS400.INI
H99_INP.TXT
H00.INI
Application Server
LINEUNIT.INI
LU002.INI
H14.INI
LU001.INI
H20.INI
1) Line specific parameters, e.g., comport
2) General protocol settings
3) Definition of lines and protocols
4) PCU general parameters
Parameters in PCU400
-
Time Synchronization by minue pulse
Time messages sent to RTU
Cyclic broadcast message (TSIL)
(Y, M, D ,h, min, sec)
Minute
pulses
Time base Application Server A
RCS Application
ASCII-string
PCU400
-
PCU400 Main Software Components
Windows XP
WIN32
Communication Port Drivers:
OCC / TCP- IP
Supervisor
Watchdog
DCU
Control Agent
Remote Access
Trap Manager
Saving of Traps
to HD
Clock
Controller
Web Server
-
Customer benefits
PCU400 is flexible
Different configurations are supported
Standard non-ABB hardware is used
Standard Windows NT 4.0
Open interfaces available e.g. DDE, XML
Protocols can be bought as 3rd part products e.g. LON
Protocols are run as separate processes in NT
Remote diagnostics via LAN or Modem
Adds functionality as new protocols to old systems
-
PCU400 replaces RCS3xx
PCU400 covers SCADA, SA and standalone configurations
PCU 400 is a component in the SPIDER system
PCU400 has potential to grow as Gateway
Reduced maintenance cost
New markets gives bigger volumes
Customer benefits Cont..
top related