Familiriazation With Rtu Software Architecture

RTU 560 Software architecture 

   .    B   1      B  .    A   d   r   e   a   v   e   r   e   y   s    t   e    h   r   g   s   1    i   r   t    1   y   h   0   p   i   g   2   o   r    /    7    C   l    l    2    A   /    ©    4

Insert image here

RTU 560 Software architecture 





      2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 high performance due to 

Effective distribution of task to the communication c ommunication and processing unit (cmu) and microcontroller on the I/O board.



Each I/O board has it own IOC (input output controller)

Different processor work independently of each other and decoupled from each other via shared memories. Different processor could handle different task independently and communicate with each other via internal system bus. Optimal execution of individual task

RTU 560 Software Package

       3      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 used 32 bit VxWork (Wind River System) Std programs are written in C programming language covering 

Telecontrol function



System monitoring



Time management



Database handling

RTU 560 Software architecture



The program system architecture is of modular design and consist of 

Microcontroller programs Standard programs



Application programs





     4      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

The PLC program for the station automation function task cyclically executed by optionally PLC software.

RTU 560 Software Structure

     5      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 Software Structure

     6      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 Software Structure

 





     7      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

The software structured into different activities Activities could run on one CMU or distributed to different CMUs The number of CMUs depend on the number of type and communication interfaces. The activities and distribution of CMUs are configured within RTUtil NT and informations are stored in the configuraion file ( *.gcd and *.iod )

RTU 560 Software Structure



IC Internal Communication 

Activities interact with each other via IC



IC provide common language to all activities defined.



     8      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

To communicate, every activities distributed it messages and each of distributed messages is received by all other activities.

RTU 560 Software Structure



System Control and time administration 





     9      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

This activitiy is running on the CMU which defined as master in Administrator Mode function Master CMU provide system control handling which provide system startup and supervision of all CMU Time sync administration is also performed by master CMU.

RTU 560 RTUtil NT : Administrator mode

     0    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 Software Structure



Board Control and Diagnosis  



     1    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

This activitiy is running on each CMU defined System startup and supervision of a CMU board is handle by this activity Web browser for diagnosis belong to this activity

RTU 560 Software Structure



PDP (process data processing) and I/O bus master 



     2    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

This activity is running on each CMU for interfaces to I/O bus segment via COM A/B Supervision and control of the I/O board

RTU 560 Software Structure



HCI Host Communication Interfaces 



     3    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©



This activity is running on each CMU for interfaces to control centre (e.g NLDC, MCC) via interfaces medium such as COM 1/2/A/B or ETH It is possible to run multiple HCI in one CMU. (e.g WISP++ and IEC 101) Each HCI handle it’s own complete communication protocol including it’s own queues and buffers

RTU 560 Software Structure



HCI Host Communication Interfaces 





     4    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

Interface to internal communication Application layer in monitoring and command direction Link layer

RTU 560 Software Structure: Host interface

     5    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

I/O module I/O module

RTU 560 Software Structure: Host interface 

     6    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

Queue and buffer handling for WISP++

RTU 560 Software Structure: Host interface 

The monitoring application layer depending on the queue priority to read out the queues and send the telegram to link layer  



     7    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©



Interface to IC get telegram Interface to IC distribute the telegram to one of the queues Depending on the priority, monitoring direction read out the queue Link layer send the telegram

RTU 560 Software Structure: Host interface 

     8    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

The Queues : RTUtil 560 Parameter

RTU 560 Software Structure



SCI Subordinate Device Communication Interfaces 



     9    1      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©



This activity is running on each CMU for interfaces to sub device protocol via interfaces medium such as COM 1/2/A/B or ETH (submaster function or com to IEDs) It is possible to run multiple SCI in one CMU. (e.g sub WISP++ and sub IEC 101 on one CPU card) Each SCI handle it’s own complete communication protocol including it’s own queues and buffers

RTU 560 Software Structure 

     0    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

SCI Subordinate Device Communication Interfaces

RTU 560 Software Structure 

SCI Subordinate Device Communication Interfaces 

Message flows in monitoring direction  Check the validity of message by link layer. For sub WISP+ , the invalid (IV flag) and health (H flag) is checked. 

     1    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

The application layer in monitoring direction decode the user data. The value and flags converted into internal msg

RTU 560 Software Structure 

SCI Subordinate Device Communication Interfaces 

Message flows in command direction  Messages is detected from IC and checked by the application layer. 



     2    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

The application encode the messages for the values, flags and encrypted to specific user protocol data. All encrypted values then send to Link layer where link information is added before sending out to subordinate line

RTU 560 Software Structure



Data Base 





     3    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

This activity is running on each CMU It collects all process message and all system status messages including all the status and qualifier (flag) for each of the point (e.g IV, OV, TIV) Web server shows the actual state of data base.

RTU 560 Software Structure 

PLC IEC 61131-3 







     4    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©



PLC activity run on the CMU which is defined to have PLC FUNCTION configured by RTUtil NT. It is possible to run PLC activity concurrently with other communication function (HCI or SCI) Communication activity is higher in priority as compared with PLC activity PLC is an integrated part of RTU 560 which exchange data with RTU560 It is possible to run PLC on different CMU as it could communicate with other CMUthrough IC bus

RTU 560 Software Structure 

PLC IEC 61131-3 processing in RTU560

CMU

     5    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

RTU 560 Software Structure



MMI Interface 





     6    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

MMI activity run on each CMU board Accessible via PPP protocol to provide Web browser facility The physical connection either through serial connection or ethernet port

RTU 560 Software Structure : Web browser 

RTU560 Web server provide 





HTML page with process diagnosis functionality HTML page with dialog for loading RTU560 configuration file



HTML page with dialog for loading RTU560 firmware file Local archive function



Administration of web server



     7    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©

HTML page with system diagnosis functionality

RTU 560 Software Structure : Web browser

     8    2      B    B    A   r   a   e   y    t    h   g    i   r   y   p   o    C    ©