Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Copy of PLC EXPERIMENT 6

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

DEPARTMENT OF ELECTRICAL ENGINEERING

Experiment No. 06

Date:____________

Title: PLC interfaced with SCADA & status read/command transfer operation.
Aim: To develop the ladder diagram in PLC and interface with SCADA and perform on of
operation in SCADA.
PLC trainer Kit: Equipment:
1.

Advanced PLC trainer Kit Allen Bradley Micrologix 1400

2.

Ladder programming software (RsLogix 500 English by AB)

3.

Communication Cable (any Ethernet Cross Cable)

4.

PC

5.

SCADA programming software( iFIX 5.0)

Advanced PLC trainer Kit:


Allen Bradley MicroLogix 1400 series 1766-L32BXB PLC with 12 Fast 24V DC Inputs,
8 Normal 24V DC Inputs, 6 Relay Outputs, 3 Fast DC Outputs, 3 Normal DC Outputs, Start,
Stop and input simulation switches, proxy sensors and lamps for outputs. 230VAC mains MCB.
Provision to connect computer via Ethernet communication port. MS fabricated, Orange Colour
powder coated frame.

DEPARTMENT OF ELECTRICAL ENGINEERING

What does SCADA mean?


SCADA stands for Supervisory Control And Data Acquisition. As the name indicates, it
is not a full control system, but rather focuses on the supervisory level. As such, it is a purely
software package that is positioned on top of hardware to which it is interfaced, in general via
Programmable Logic Controllers (PLC's), or other commercial hardware modules.
SCADA systems are used not only in industrial processes but also in some experimental
facilities such as nuclear fusion. The size of such plants range from a few 1000 to several 10
thousands input/output (I/O) channels. However, SCADA systems evolve rapidly and are now
penetrating the market of plants with a number of I/O channels of several 100 thousands I/O's
1. Architecture
This

section

describes

the

common

Hardware Architecture

features

of

the

SCADA

products.

DEPARTMENT OF ELECTRICAL ENGINEERING

One distinguishes two basic layers in a SCADA system: the "client layer" which caters
for the man machine interaction and the "data server layer" which handles most of the
process data control activities.

Figure 1: Typical Hardware Architecture

Software Architecture
The products are multi-tasking and are based upon a real-time database (RTDB) located
in one or more servers. Servers are responsible for data acquisition and handling (e.g. polling
controllers, alarm checking, calculations, logging and archiving) on a set of parameters, typically
those they are connected to.

DEPARTMENT OF ELECTRICAL ENGINEERING

Figure 2: Generic Software Architecture


However, it is possible to have dedicated servers for particular tasks, e.g. historian,
datalogger, alarm handler. The figure above shows a generic SCADA software architecture.
Communications
Internal Communication:
Server-client and server-server communication is in general on a publish-subscribe and
event-driven basis and uses a TCP/IP protocol, i.e., a client application subscribes to a parameter
which is owned by a particular server application and only changes to that parameter are then
communicated to the client application.
Access to Devices:
The products provide communication drivers for most of the common PLC's and widely
used field-buses, e.g., Modbus. Some of the drivers are based on third party products (e.g.,
Applicom cards) and therefore have additional cost associated with them. VME on the other
hand is generally not supported.
A single data server can support multiple communications protocols: it can generally
support as many such protocols as it has slots for interface cards.

DEPARTMENT OF ELECTRICAL ENGINEERING

Interfacing
Application Interfaces / Openness:
The provision of OPC client functionality for SCADA to access devices in an open and
standard manner is developing.
The products also provide an Open Data Base Connectivity (ODBC) interface to the data
in the archive/logs, The API often does not provide access to the product's internal features such
as alarm handling, reporting, trending, etc.
The PC products provide support for the Microsoft standards such as Dynamic Data
Exchange (DDE) which allows e.g. to visualize data dynamically in an EXCEL spreadsheet,
Dynamic Link Library (DLL) and Object Linking and Embedding (OLE).
Database:
The configuration data are stored in a database that is logically centralized but physically
distributed and that is generally of a proprietary format. The archive and logging format is
usually also proprietary for performance reasons, but some products do support logging to a
Relational Data Base Management System (RDBMS) at a slower rate either directly or via an
ODBC interface.
Scalability
The products achieve scalability by having multiple data servers connected to multiple
controllers. Each data server has its own configuration database and RTDB and is responsible for
the handling of a sub-set of the process variables (acquisition, alarm handling, archiving).
Redundancy
The products often have built in software redundancy at a server level, which is normally
transparent to the user.
2. Functionality

DEPARTMENT OF ELECTRICAL ENGINEERING

Access Control
Users are allocated to groups, which have defined read/write access privileges to the
process parameters in the system and often also to specific product functionality.
MMI
The products support multiple screens, which can contain combinations of synoptic
diagrams and text.
Most of the SCADA products that were evaluated decompose the process in "atomic"
parameters (e.g. a power supply current, its maximum value, its on/off status, etc.) to which a
Tag-name is associated. The Tag-names used to link graphical objects to devices can be
edited as required. The products include a library of standard graphical symbols.
Standard windows editing facilities are provided: zooming, re-sizing, scrolling... On-line
configuration and customization of the MMI is possible for users with the appropriate
privileges. Links can be created between display pages to navigate from one view to another.
Trending
The products all provide trending facilities and one can summarize the common
capabilities as follows:
The parameters to be trended in a specific chart can be predefined or defined on-line
a chart may contain more than 8 trended parameters or pens and an unlimited number of
charts

can

be

displayed

(restricted

only

by

the

readability)

real-time and historical trending are possible, although generally not in the same chart
historical

trending

zooming
parameter

is

and
values

possible
scrolling

at

the

for

any

functions
cursor

position

archived

parameter

are

provided

can

be

displayed

Alarm Handling
Alarm handling is based on limit and status checking and performed in the data servers.
The alarms are logically handled centrally, i.e., the information only exists in one place and

DEPARTMENT OF ELECTRICAL ENGINEERING

all users see the same status (e.g., the acknowledgement), and multiple alarm priority levels
(in general many more than 3 such levels) are supported.It is possible to suppress alarms
either individually or as a complete group. The filtering of alarms seen on the alarm page or
when viewing the alarm log is also possible at least on priority, time and group.
Logging/Archiving
Logging can be thought of as medium-term storage of data on disk, whereas archiving is
long-term storage of data either on disk or on another permanent storage medium. Logging is
typically performed on a cyclic basis. Logged data can be transferred to an archive once the
log is full. The logged data is time-stamped and can be filtered when viewed by a user.
Report Generation:
One can produce reports using SQL type queries to the archive, RTDB or logs. Although
it is sometimes possible to embed EXCEL charts in the report. Facilities exist to be able to
automatically generate, print and archive reports.
Automation
The majority of the products allow actions to be automatically triggered by events. A
scripting language provided by the SCADA products allows these actions to be defined.
The concept of recipes is supported, whereby a particular system configuration can be saved
to

file

and

then

re-loaded

at

later

date.

Sequencing is also supported whereby, as the name indicates, it is possible to execute a


more complex sequence of actions on one or more devices.
3. Application Development
Configuration
The development of the applications is typically done in two stages. First the process
parameters and associated information (e.g. relating to alarm conditions) are defined through

DEPARTMENT OF ELECTRICAL ENGINEERING

some sort of parameter definition template and then the graphics, including trending and
alarm displays are developed, and linked where appropriate to the process parameters.
Development Tools
The

following

development

tools

are

provided

as

standard:

Graphics Editor, with standard drawing facilities including freehand, lines, squares circles,
etc. It is possible to import pictures in many formats as well as using predefined symbols
including e.g. trending charts, etc. A library of generic symbols is provided that can be linked
dynamically to variables and animated as they change. It is also possible to create links
between views so as to ease navigation at run-time.
Database Configuration Tool (usually through parameter templates). It is in general
possible to export data in ASCII files so as to be edited through an ASCII editor or Excel.
Scripting Language
Application

Program

Interface

(API)

supporting

C,

C++,

VB

Driver Development Toolkit to develop drivers for hardware that is not


Supported by the SCADA product.
4. Evolution
SCADA vendors release one major version and one to two additional minor versions
once per year. These products evolve thus very rapidly so as to take advantage of new market
opportunities, to meet new requirements of their customers and to take advantage of new
technologies.
As was already mentioned, most of the SCADA products that were evaluated decompose
the process in "atomic" parameters to which a Tag-name is associated. This is impractical in
the case of very large processes when very large sets of Tags need to be configured. As the
industrial applications are increasing in size, new SCADA versions are now being designed
to handle devices and even entire systems as full entities (classes) that encapsulate all their
specific attributes and functionality. In addition, they will also support multi-team
development.

DEPARTMENT OF ELECTRICAL ENGINEERING

As far as new technologies are concerned, the SCADA products are now adopting:
Web technology, ActiveX, Java, etc.
OPC as a means for communicating internally between the client and server modules. It
should thus be possible to connect OPC compliant third party modules to that SCADA
product.

Procedure:
A) Precautions:
1. Ensure following points for proper functioning of the trainer.
2. Mains supply is 230VAC 10% 50HZ.
3. All input simulation switches are in off position [Toggle to Down side ],
4. At power ON, no any module is interfaced or cables are connected.
5. Mains MCB switch is OFF.

B) Experimental Procedure:
1. Ensure mains supply is 230VAC 10% 50HZ.
2. Connect the mains cable and turn ON the Mains MCB.
3. Ensure the power ON LED on the PLC module lit.
4. Toggle the input simulation switches and observe the appropriate input block lit on LCD.
5. Those operation you have performed in PLC -SCADA,& define related tag in IGS

6.

Open IGS ---> Select channel 1----> Select device 1 ----> Click right button on mouse &

define NEW tag ---->Define tag name in identification - name block (e.g.start,stop,on,off etc)
----> Define tag address (e.g. B3:0/n, n =1,2,3..20)----->Apply ----> Ok ----> Save this
tag in PLC
7. Develop application related Ladder diagram in PLC
8. Open iFIX SCADA 5.5----> click tool bar application ----> open Data base manager ---->
open local node ----> ok ----> define same tag in PLC to SCADA ----> Save this tag in SCADA

DEPARTMENT OF ELECTRICAL ENGINEERING

----> Close data base manager -----> open dynamo set in home screen ----> drag to appropriate
application
----> open new picture ----> Define appropriate tag related application in iFIX SCADA 5.0
9. Run SCADA
C) Shut down procedure:
1. Disconnect all interfacing modules/ devices.
2. Switch off mains and remove mains cable.
3. Store the trainer along with all accessories in safe custody.

Questions:
1) To develop ladder diagram of Lamp & push button operation with start & stop operation.
Conclusion:

10

You might also like