PCU 400 Product Presentation

Embedded Type

General Models

PCU 400 as Front-End

Applicatio
n
Servers

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

RSP protocol over

Ethernet or RS-232

PCU 400

Available RTU protocols

NG

ZG
WT

15

RTU or
SCS system

PCU 400 as Concentrator for SA and SCADA

Functions:

Remote Master
Systems

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

F.ex. IEC870-5-101

Configuration Tool
NG

ZG
WT

15

NG

ZG
WT

15

RTU or
Protection relay

PCU 400 as Converter

Functions:
Remote
Master System

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

F.ex. IEC870-5-101

Configuration Tool
F.ex. Indactic 2033

NG

ZG
WT

15

RTU or
SA system

PCU 400 Host www-server

Current value

The PCU400 also supports webinterface for some protocols for

remote debugging

Event list

Logging
Device status

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

PCU400 Communication Module(OCC Unit)

OCC (Octal Communication

Controller) is a device that enables

distribution of serial communication
ports through ethernet based
networks

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

OCC Unit connected to PCU through a hub or switch
IP Address assigned to OCC through DHCP protocol

Ethernet
1

Ethernet
1

Ethernet

HUB
1

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

PCU 400 Connection to SPIDER

Main Computer A (Linux)

Main Computer B (Linux)

Rest of SPIDER

Rest of SPIDER

RCS Application

RCS Application

LAN or WAN

RSP Links
PCU400 A

PCU400 B

RTU lines

PCU400 Distributed Functionality

The Data Acquisition System is distributed
in two software components:
RCS Application

RCS Application

residing in SPIDER

Supervision of PCU connection

Handling of line switchover
PCU400

Handling

via TCP/IP comports

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

PCU 400 Data flow - SCADA

PCU400

MMI

RSP Protocol

API/
Queue

Line/Data Supervision

Customer data

API/
Queue

B Module
Avanti Database Avanti

Data
Engineering

RCS Database
Population

RCS

SPIDER (SCADA Servers)

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
Application Server B

Application Server A

RCS Application A

RCS Application B

LAN 1
LAN 2

2
RSP lines

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

PCU400 A

PCU400 B

3
Line switch

RTU

RTU lines

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

Database-Object level
Line Pool 1 = Com line 1
Line Pool/
Com line

Line Unit 1
Line Unit 1

Line Unit 2

Line Unit x

Line Unit 2

Line Unit 3

Hardware
level

LAN or WAN

PCU 1

PCU 2

Each Line Unit side is

connected to a PCU
number
The PCU can be distributed

Ch 1A Ch 2A Ch xA

Ch 1B Ch 2B Ch xB

Each RTU belongs to one

Line Pool
Line switch only if
redundant PCUs

Line Switch
Line 1, to RTU

Line Switch
Line 2, to RTU

Parameters in PCU400
Application Server

RCS400.INI
H99_INP.TXT
H00.INI

1) Line specific parameters, e.g., comport

PCU400

2) General protocol settings

LINEUNIT.INI

3) Definition of lines and protocols

SW bus (RSP)

4) PCU general parameters

H20.INI

LU001.INI

H14.INI

LU002.INI

Time Synchronization by minue pulse

Application Server A
RCS Application

Time base

ASCII-string
Cyclic broadcast message (TSIL)
(Y, M, D ,h, min, sec)

PCU400

Time messages sent to RTU

Minute
pulses

PCU400 Main Software Components

Supervisor
Watchdog
Control Agent
Remote Access

Windows XP
DCU
WIN32

Trap Manager
Saving of Traps
to HD
Clock
Controller

Communication Port Drivers:

OCC / TCP- IP

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

Customer benefits Cont..

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