PLC AND SCADA AUTOMATION

SUBMITTED
IN THE PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE AWARD OF DEGREE OF

BACHELOR OF TECHNOLOGY

In

Electronics and Communication Engineering

SUBMITTED BY

YOGESH SINGH
Uni. Roll No.100320415236
Branch- ECE
Semester-8th

GGS COLLEGE OF MODERN TECHNOLOGY, KHARAR

PUNJAB TECHANICAL UNIVERSITY, JALANDHAR
 ACKNOWLEDGEMENT

I express my sincere gratitude to the Punjab Technical University, Jalandhar for giving me the
opportunity to work on the training during my 4th year of B.Tech.
I would like to thank Dr.N.S.Biradar, Director, and Ms. Mandeep Sharma HOD-ECE of GGS
College of Modern Technology, Kharar for their kind support.

I also owe my sincerest gratitude towards Training incharge Ms.Mukta Sharma ECE
Department for her valuable advice and healthy criticism throughout my training which helped
me immensely to complete my work successfully.

YOGESH SINGH
Uni. Roll No.100320415236

i
CERTIFICATE

ii
 ABSTRACT

An industrial PLCs & SCADA AUTOMATION system is used for the development of the
controls of machinery. This paper describes the SCADA & PLCs systems in terms of their
architecture, their interface to the process hardware, the functionality and the application
development facilities they provide .Some attention is also paid to the industrial standards to
which they abide their planned evolution as well as the potential benefits of their use.

Major project work aims at developing innovative skills in the students whereby they apply in. In
addition, the project work is intended to place students. For project oriented practical training in
actual work situation for the stipulated period with a view to:
 Develop understanding regarding the size and scale of operations and fieldwork in which
students are going to play their role.

 Develop understanding of subject based knowledge given in the classroom in the context of
its application at work places.

 Develop experience and confidence amongst the student to enable them to use and apply
knowledge and skills to solve practical problems.

 Develop abilities like interpersonal skills, communication skills, positive attitude and values
etc.

The project should be selected in such a manner that after completion it should have practical use
at the same time it should be interesting also but before starting any project, market survey is
very important. By market survey we are able to know whether the components are available in
the market, the selection of project should be on the following basis:-
 The project should be such a type, that the maximum work can be done with our hands.

 It should be within the facilities available in the shop and labs.

 oretical knowledge of the subject should be clear.

iii
 LIST OF FIGURES

Figure Caption of Figure Page

No. No.
Fig.2.2 Allen-Bradley PLC 5

Fig.2.3 Block diagram of PLC 6

Fig.2.3(a) Diagram showing energized input terminal X1 7

Fig.2.3(b) Diagram showing energized output terminal Y1 9

Fig.3.3(a) Connections 18

Fig.3.3(b) Connections 19

Fig.4 Initial state of motor 21

Fig.4.1(a) Logic for continuous running of motor 22

Fig.4.1(b) To stop the motor 23

Fig.4.1(c) Input X2 is de-energized 24

Fig.4.3(a) CoDeSys software 28

Fig.4.3(b) Target settings 29

Fig.4.3(c) New POU 29

Fig.4.3(d) File is started to work 30

Fig.5.2 Architecture of SCADA 34

Fig.7.1(a) Programming on CoDeSys 43

Fig.7.1(b) Visualization 43

Fig.7.2(a) Programming on CoDeSys 45

Fig.7.2(b) Visualization 45

Fig.7.3(a) Programming on CoDeSys 46

iv
Fig.7.4(a) Programming on CoDeSys 47

Fig.7.4(b) Visualization 48

v
 LIST OF ABBREVIATIONS

Abbreviation Meaning

I/P Input
O/P Output
LED Light emitting diode
PLC Programmable Logic Controller
SCADA Supervisory Control and Data Acquisition
R&D Research & development
PID Proportional integral derivative
DCS distributed con
CFC Continuous function chart
LD Ladder diagram
DC Direct current
AC Alternate current
IEC International Electrotechnical commission
POU Program organization unit
IL Instruction list
ST Structured list
SFC Sequential function chart
FBD Function block development
ASCII American standard code for information interchange
RDMBS Relational data base management system
VB Visual basic
TCP Transmission control protocol
IP Internet protocol

vi
 TABLE OF CONTENTS

Contents Page no.

Acknowledgement i
Certificate ii
Abstract iii
List of Figures iv- v
List of Abbreviations vi

Chapter 1

COMPANY PROFILE 1-3

Chapter 2 4-11
PLC

2.1 Introduction 4
2.2 Features of PLC 5
2.3 Wiring in PLC 6-9
2.4 PLC compared with other control systems 9-10
2.5Digital and analog signals 10
2.6 Example 11

Chapter 3 12-20

vii
Programming with PLC

3.1Ladder logic 12-14

3.2Generally used instruction & symbol for plc programming 14-15
3.3For example 15-20

Chapter 4 21-39
Programming for Start/Stop of Motor by PLC

4.1 Starting of motor 22-24

4.2 A brief introduction to CoDeSys 24-27
4.3 Creating started with CoDeSys 27-32

Chapter 5 33-39
SCADA

5.1 Meaning of SCADA 33

5.2 Architecture 34
5.3 Communication 35
5.4 Interfacing 36-37
5.5 Functionality 37-38
5.6 Alarm handling 38
5.7 Logging/Archiving 39
5.8 Report generation 39
5.9 Automation 39

viii
Chapter 6 40-42
Application & development in SCADA
6.1 Configuration 40
6.2 Development tools 41
6.3 Evolution 41
6.4 Engineering 42
6.5 potential benefits of SCADA 42

Chapter 7 43-48
Projects examples

7.1 Problem 1: Lighting 3 bulb using 2 switches. 43-44

7.2 Problem 2: 3 inputs1 output, any two input are used to light up the output. 45
7.3 Problem 3: Auto door lamp. 46
7.4 Problem 4: Auto drill application. 47-48

CONCLUSION ix
LIMITATION ixi
PRACTICAL SCOPE OF TRAINING ixi
BIBLIOGRAPHY ixii

ix
 CHAPTER 1

COMPANY PROFILE

Netmax Technologies is an organization which is established in the field of Network Support,

Network training and Embedded systems. We provide Support and training in the field of
networking solutions (CISCO, LINUX) and embedded systems (Micro controller based design,
Electronics system design).
In Education we have strategic alliance with REDHAT Inc. We are also NOVELL
EDUCATION PARTNER with which we provide NOVELL and SUSE LINUX courses. Netmax
technologies also conduct courses in CADENCE based design tools. Netmax Technologies also
provide Technical Research & Development support and consultancy to some Electronics
companies.

Our clients for R&D support in field of embedded systems:

1) Recorders and Medicare ltd Chandigarh.

2) TELEBOX India ltd.
3) Lotus Machines Pvt. Ltd. Chandigarh.
4) Impearl Electronics Pvt. Ltd. Chandigarh.
5) KANTA Electrical Ltd. Mohali.

The partial list of our clientele for network field is as below:

1) CEDTI, Mohali
2) Premier ISP, Chandigarh
3) Innovative Solutions, Chandigarh
4) Emmtel ISP, Chandigarh
5) NIPER, Mohali

1
6) Navik Technologies, Chandigarh
7) Software Technology Parks India, Mohali
8) Glide Internet Services
9) Rana Group
10) IDS
11) HFCL Infotel Ltd.
12) Targus technologies pvt ltd
13) STPI, Mohali
14) BBMB
15) The Tribune
16) Quark
17) Ind Swift

OUR TEAM
Presently we have a strong technical team of certified professionals for catering to these
solutions and have presence in Chandigarh and Punjab. We have skilled team of engineers who
are experienced in design, programming. We are having more than 10 engineers who are having
prestigious certifications like CCNA, CCNP, CCSE, MCSE and RHCE.

Support Area (network solutions)

a) LINUX / UNIX networks
b) SUN networks
c) CISCO devices (Routers, Switches, Firewalls, Cache Engine, RAS etc)
d) Bandwidth Manager software and hardware
e) Radio Links
f) Security Solutions

Design Services (Embedded systems)

a) AVR family
b) MCS 51
c) ELECTRONIC SYSTEM DESIGN

2
Network Training
a) CISCO CCNA, CCNP
b) RED HAT LINUX
c) SUN SOLARIS
d) WINDOWS 2000, 2003

Our core strength is our commitment, technical expertise and cost effective solutions. We ensure
high service levels and prompt support availability leading to lower downtime.

Netmax Technologies is a leader in education services and developer of innovative embedded

solutions. To meet the demands of Post PC era Netmax provides complete solutions as well as
design-to-order services to satisfy our customers.

3
 CHAPTER- 2
PLC

2.1 Introduction

A Programmable Logic Controller, PLC, or Programmable Controller is a digital computer used

for automation of industrial processes, such as control of machinery on factory assembly lines.
Unlike general-purpose computers, the PLC is designed for multiple inputs and output
arrangements, extended temperature ranges, immunity to electrical noise, and resistance to
vibration and impact. Programs to control machine operation are typically stored in battery
backed or non-volatile memory. A PLC is an example of a real time system since output results
must be produced in response to input conditions within a bounded time, otherwise unintended
operation will result.

PLC and Programmable Logic Controller are registered trademarks of the Allen-Bradley
Company.

SCADA is widely used in industry for Supervisory Control and Data Acquisition of industrial
processes. SCADA systems are now also penetrating the experimental physics laboratories for
the controls of ancillary systems such as cooling, ventilation, power distribution, etc. More
recently they were also applied for the controls of smaller size particle detectors such as the L3
moon detector and the NA48 experiment, to name just two examples at CERN.

SCADA systems have made substantial progress over the recent years in terms of functionality,
scalability, performance and openness such that they are an alternative to in house development
even for very demanding and complex control systems as those of physics experiments.

4
2.2. Features of PLCs

Figure 2.2-Photograph showing several input and output modules of a single Allen-Bradley
PLC

With each module having sixteen "points" of either input or output, this PLC has the ability to
monitor and control dozens of devices. Fit into a control cabinet, a PLC takes up little room,
especially considering the equivalent space that would be needed by electromechanical relays to
perform the same functions.
The main difference from other computers is that PLC are armored for severe condition (dust,
moisture, heat, cold, etc) and has the facility for extensive input/output (I/O) arrangements.
These connect the PLC to sensors and actuators. PLCs read limit switches, analog process
variables (such as temperature and pressure), and the positions of complex positioning systems.
Some even use machine vision. On the actuator side, PLCs operate electric motors, pneumatic or
hydraulic cylinders, magnetic relays or solenoids, or analog outputs. The input/output

5
arrangements may be built into a simple PLC, or the PLC may have external I/O modules
attached to a computer network that plugs into the PLC.
Many of the earliest PLCs expressed all decision making logic in simple ladder logic which
appeared similar to electrical schematic diagrams. The electricians were quite able to trace out
circuit problems with schematic diagrams using ladder logic. This program notation was chosen
to reduce training demands for the existing technicians. Other early PLCs used a form of
instruction list programming, based on a stack-based logic solver.
The functionality of the PLC has evolved over the years to include sequential relay control,
motion control, process control, distributed control systems and networking. The data handling,
storage, processing power and communication capabilities of some modern PLCs are
approximately equivalent to desktop computers.

2.3 Wiring in a PLC

Figure 2.3 – Block diagram of PLC

6
2.3.1 Generation of Input Signal

Inside the PLC housing, connected between each input terminal and the Common terminal, is an
opto-isolator device (Light-Emitting Diode) that provides an electrically isolated "high" Logic
signal to the computer's circuitry (a photo-transistor interprets the LED's light) when there is 120
V AC power applied between the respective input terminal and the Common terminal. An
indicating LED on the front panel of the PLC gives visual indication of an "energized" input.

Figure 2.3(a) – Diagram showing energized input terminal X1

7
2.3.2 Generation of Output Signal

Output signals are generated by the PLC's computer circuitry activating a switching device
(transistor, TRIAC, or even an electromechanical relay), connecting the "Source" terminal to
any of the "Y-" labeled output terminals.
The "Source" terminal, correspondingly, is usually connected to the L1 side of the 120 VAC
power source. As with each input, an indicating LED on the front panel of the PLC gives visual
indication of an "energized" output.

In this way, the PLC is able to interface with real-world devices such as switches and solenoids.
The actual logic of the control system is established inside the PLC by means of a computer
program. This program dictates which output gets energized under which input conditions.

Although the program itself appears to be a ladder logic diagram, with switch and relay symbols,
there are no actual switch contacts or relay coils operating inside the PLC to create the logical
relationships between input and output. These are imaginary contacts and coils, if you will. The
program is entered and viewed via a personal computer connected to the PLC's programming
port.

8
Figure 2.3(b) - Diagram showing energized output Y1

2.4 PLC compared with other control systems

PLCs are well-adapted to a certain range of automation tasks. These are typically industrial
processes in manufacturing where the cost of developing and maintaining the automation system
is high relative to the total cost of the automation, and where changes to the system would be
expected during its operational life. PLCs contain input and output devices compatible with
industrial pilot devices and controls; little electrical design is required, and the design problem
centers on expressing the desired sequence of operations in ladder logic (or function chart)
notation. PLC applications are typically highly customized systems so the cost of a packaged
PLC is low compared to the cost of a specific custom-built controller design. For high volume or
very simple fixed automation tasks, different techniques are used.
A microcontroller-based design would be appropriate where hundreds or thousands of units will
be produced and so the development cost (design of power supplies and input/output hardware)

9
can be spread over many sales, and where the end-user would not need to alter the control.
Automotive applications are an example; millions of units are built each year, and very few end-
users alter the programming of these controllers. However, some specialty vehicles such as
transit busses economically use PLCs instead of custom-designed controls, because the volumes
are low and the development cost would be uneconomic.
PLCs may include logic for single-variable feedback analog control loop, a "proportional,
integral, derivative" or "PID controller." A PID loop could be used to control the temperature of
a manufacturing process, for example. Historically PLCs were usually configured with only a
few analog control loops; where processes required hundreds or thousands of loops, a distributed
control system (DCS) would instead be used. However, as PLCs have become more powerful,
the boundary between DCS and PLC applications has become less clear.

2.5 Digital and analog signals

Digital or discrete signals behave as binary switches, yielding simply an on or Off signal (1 or 0,
True or False, respectively). Pushbuttons, limit switches, and photoelectric sensors are examples
of devices providing a discrete signal. Discrete signals are sent using voltage or current, where a
specific range is designated as on and another as off. For example, a PLC might use 24V DC I/O,
with values above 22V DC representing on, values below 2V DC representing off and
intermediate values undefined. Initially, PLCs had only discrete I/O.
Analog signals are like volume controls, with a range of values between zero and full-scale.
These are typically interpreted as integer values (counts) by the PLC, with various ranges of
accuracy depending on the device and the number of bits available to store the data. As PLCs
typically use 16-bit signed binary processors, the integer values are limited between -32,768 and
+32,767. Pressure, temperature, flow, and weight are often represented by analog signals.
Analog signals can use voltage or current with a magnitude proportional to the value of the
process signal. For example, an analog 4-20 mA or 0 - 10 V input would be converted into an
integer value of 0 - 32767.
Current inputs are less sensitive to electrical noise (i.e. from welders or electric motor starts)
than Voltage inputs.

10
2.6 Example

As an example, say the facility needs to store water in a tank. The water is drawn from the tank
by another system, as needed, and our example system must manage the water level in the tank.
Using only digital signals, the PLC has two digital inputs from float switches (tank empty and
tank full). The PLC uses a digital output to open and close the inlet valve into the tank.
If both float switches are off (down) or only the 'tank empty' switch is on, the PLC will open the
valve to let more water in. Once the 'tank full' switch is on, the PLC will automatically shut the
inlet to stop the water from overflowing. If only the 'tank full' switch is on, something is wrong
because once the water reaches a float switch, the switch will stay on because it is floating, thus,
when both float switches are on, the tank is full. Two float switches are used to prevent a 'flutter'
(a ripple or a wave) condition where any water usage activates the pump for a very short time
and then deactivates for a short time, and so on, causing the system to wear out faster.
An analog system might use a load cell (scale) that weighs the tank, and an adjustable (throttling)
valve. The PLC could use a PID feedback loop to control the valve opening. The load cell is
connected to an analog input and the valve is connected to an analog output. This system fills the
tank faster when there is less water in the tank. If the water level drops rapidly, the valve can be
opened wide. If water is only dripping out of the tank, the valve adjusts to slowly drip water back
into the tank.
A real system might combine approaches, using float switches and simple valves to prevent
spills, and a rate sensor and rate valve to optimize refill rates. Backup and maintenance methods
can make a real system very complicated.

11
 CHAPTER 3
Programming with PLC

Early PLCs, up to the mid-1980s, were programmed using proprietary programming panels or
special-purpose programming terminals, which often had dedicated function keys representing
the various logical elements of PLC programs. Programs were stored on cassette tape cartridges.
Facilities for printing and documentation were very minimal due to lack of memory capacity.
More recently, PLC programs are typically written in a special application on a personal
computer and then downloaded by a direct-connection cable or over a network to the PLC. The
very oldest PLCs used non-volatile magnetic core memory but now the program is stored in the
PLC either in battery-backed-up RAM or some other non-volatile flash memory.
Early PLCs were designed to be used by electricians who would learn PLC programming on the
job. These PLCs were programmed in "ladder logic", which strongly resembles a schematic
diagram of relay logic. Modern PLCs can be programmed in a variety of ways, from ladder logic
to more traditional programming languages such as BASIC and C. Another method is State
Logic, a Very High Level Programming Language designed to program PLCs based on State
Transition Diagrams.

3.1 Ladder logic

Ladder logic is a method of drawing electrical logic schematics. It is now a graphical language
very popular for programming Programmable Logic Controllers (PLCs). It was originally
invented to describe logic made from relays. The name is based on the observation that programs
in this language resemble ladders, with two vertical "rails" and a series of horizontal "rungs"
between them.
A program in ladder logic, also called a ladder diagram, is similar to a schematic for a set of
relay circuits. An argument that aided the initial adoption of ladder logic was that a wide variety
of engineers and technicians would be able to understand and use it without much additional
training, because of the resemblance to familiar hardware systems. (This argument has become

12
less relevant given that most ladder logic programmers have a software background in more
conventional programming languages, and in practice implementations of ladder logic have
Characteristics — such as sequential execution and support for control flow features — that
make the analogy to hardware somewhat imprecise.)
Ladder logic is widely used to program PLCs, where sequential control of a process or
manufacturing operation is required. Ladder logic is useful for simple but critical control
systems, or for reworking old hardwired relay circuits. As programmable logic controllers
became more sophisticated it has also been used in very complex automation systems.
Ladder logic can be thought of as a rule-based language, rather than a procedural language. A
"rung" in the ladder represents a rule. When implemented with relays and other
electromechanical devices, the various rules "execute" simultaneously and immediately. When
implemented in a programmable logic controller, the rules are typically executed sequentially by
software, in a loop. By executing the loop fast enough, typically many times per second, the
effect of simultaneous and immediate execution is obtained. In this way it is similar to other rule
based languages, like spreadsheets or SQL. However, proper use of programmable controllers
requires understanding the limitations of the execution order of rungs.

3.1.1 Example of a simple ladder logic program

The language itself can be seen as a set of connections between logical checkers (relay contacts)
and actuators (coils). If a path can be traced between the left side of the rung and the output,
through asserted (true or "closed") contacts, the rung is true and the output coil storage bit is
asserted (1) or true. If no path can be traced, then the output is false (0) and the "coil" by analogy
to electromechanical relays is considered "de-energized". The analogy between logical
propositions and relay contact status is due to Claude Shannon.
Ladder logic has "contacts" that "make" or "break" "circuits" to control "coils." Each coil or
contact corresponds to the status of a single bit in the programmable controller's memory. Unlike
electromechanical relays, a ladder program can refer any number of times to the status of a single
bit, equivalent to a relay with an indefinitely large number of contacts.

13
So-called "contacts" may refer to inputs to the programmable controller from physical devices
such as pushbuttons and limit switches, or may represent the status of internal storage bits which
may be generated elsewhere in the program.
Each rung of ladder language typically has one coil at the far right. Some manufacturers may
allow more than one output coil on a rung.

--( )-- a regular coil, true when its rung is true

--(\)-- a "not" coil, false when its rung is true

--[ ]-- A regular contact, true when its coil is true (normally false)

--[\]-- A "not" contact, false when its coil is true (normally true)

The "coil" (output of a rung) may represent a physical output which operates some device
connected to the programmable controller, or may represent an internal storage bit for use
elsewhere in the program.

3.2 Generally used instructions & symbol for PLC programming

Input Instruction

-- [ ] -- This Instruction is Called IXC or Examine If Closed.

i.e.; If a NO switch is actuated then only this instruction will be true. If a NC switch is
actuated then this instruction will not be true and hence output will not be generated.

-- [\] -- This Instruction is Called IXO or Examine If Open

i.e.; If a NC switch is actuated then only this instruction will be true. If a NC switch is
actuated then this instruction will not be true and hence output will not be generated.

14
Output Instruction

-- ( ) -- This Instruction Shows the States of Output.

i.e.; if any instruction either XIO or XIC is true then output will be high. Due to high
output a 24 volt signal is generated from PLC processor.

Rung

Rung is a simple line on which instruction are placed and logics are created

E.g.; ---------------------------------------------

Here is an example of what one rung in a ladder logic program might look like. In real life, there
may be hundreds or thousands of rungs.

3.3 For example

1. -----[ ]----------|--[ ]---|------( )--

X | Y | S
| |
|---[ ]--|
Z

The above realizes the function: S = X AND (Y OR Z)

Typically, complex ladder logic is 'read' left to right and top to bottom. As each of the lines (or
rungs) are evaluated the output coil of a rung may feed into the next stage of the ladder as an

15
input. In a complex system there will be many "rungs" on a ladder, which are numbered in order
of evaluation.

1. ----- [ ] -----------|--- [ ] ---|---- ( )--

X | Y | S
| |
|----[ ]----|
Z
2. ---- [ ] ------------- [ ] ------------------- ( )--
S X T

T = S AND X where S is equivalent to #1 above

This represents a slightly more complex system for rung 2. After the first line has been
evaluated, the output coil (S) is fed into rung 2, which is then evaluated and the output coil T
could be fed into an output device (buzzer, light etc.) or into rung 3 on the ladder. (Note that the
contact X on the 2nd rung serves no useful purpose, as X is already a 'AND' function of S from
the 1st rung.)

This system allows very complex logic designs to be broken down and evaluated.

3.3.1 More practical examples

Example-1

------[ ]----------------------[ ]--------------------()---

Key Switch 1 Key Switch 2 Door Motor

16
This circuit shows two key switches that security guards might use to activate an electric motor
on a bank vault door. When the normally open contacts of both switches close, electricity is able
to flow to the motor which opens the door. This is a logical AND.

Example-2

Often we have a little green "start" button to turn on a motor, and we want to turn it off with abig
red "Stop" button.

-------+----[ ]---+----------[\]--------------( )---

| start | stop run
| |
+-----[ ]---+
run

-------[ ]--------------------( )---

Run motor

Example with PLC

Consider the following circuit and PLC program:

-------[ ]---------------( )---

Run motor

When the pushbutton switch is unsaturated, no power is sent to the X1 input of the PLC.
Following the program, which shows a normally open X1 contact in series with a Y1 coil, no

17
"power" will be sent to the Y1 coil. Thus, the PLC's Y1 output remains de-energized, and the
indicator lamp connected to it remains dark.
If the pushbutton switch is pressed, however, power will be sent to the PLC's X1 input. Any and
all X1 contacts appearing in the program will assume the actuated (non-normal) state, as though

Figure 3.3.1(a) -Connections

They were relay contacts actuated by the energizing of a relay coil named "X1". In this case,
energizing the X1input will cause the normally-open X1 contact will "close," sending "power" to
the Y1 coil. When the Y1coilof the program "energizes," the real Y1 output will become
energized, lighting up the lamp connected to it:

18
Lamp Glows when at Input Switch is Actuated.

Figure 3.1.1(b) - Connections

It must be understood that the X1 contact, Y1 coil, connecting wires, and "power" appearing in
the personal computer's display are all virtual. They do not exist as real electrical components.
They exist as commands in a computer program -- a piece of software only -- that just happens
that resemble a real relay schematic diagram.
Equally important to understand is that the personal computer used to display and edit the PLC's
program is not necessary for the PLC's continued operation. Once a program has been loaded to
the PLC from the personal computer, the personal computer may be unplugged from the PLC,
and the PLC will continue to follow the programmed commands. I include the personal computer
display in these illustrations for your sake only, in aiding to understand the relationship between
real-life conditions (switch closure and lamp status) and the program's status ("power" through
virtual contacts and virtual coils). The true power and versatility of a PLC is revealed when we
want to alter the behavior of a control system. Since the PLC is a programmable device, we can
alter its behavior by changing the commands we give it, without having to reconfigure the

19
electrical components connected to it. For example, suppose we wanted to make this switch-and-
lamp circuit function in an inverted fashion: push the button to make the lamp turn off, and
release it to make it turn on. The "hardware" solution would require that a normally closed
pushbutton switch be substituted for the normally-open switch currently in place. The "software"
solution is much easier: just alter the program so that contact X1 is normally-closed rather than
normally-open.

20
 CHAPTER 4

Programming For Start/Stop of Motor by PLC

Often we have a little green "start" button to turn on a motor, and we want to turn it off with a
big red "Stop" button.

---+------[ ]--------+--------[\]----------------( )---

| start | stop run
| |
+------[ ]--------+
run

Figure 4- initial state of motor i.e. in rest state

21
The pushbutton switch connected to input X1 serves as the "Start" switch, while the switch
connected to input X2 serves as the "Stop." Another contact in the program, named Y1, uses the
output coil status as a seal-in contact, directly, so that the motor contactor will continue to be
energized after the "Start" pushbutton switch is released. You can see the normally-closed
contact X2 appear in a colored block, showing that it is in a closed ("electrically conducting")
state.

4.1 Starting of Motor

If we were to press the "Start" button, input X1 would energize, thus "closing" the X1 contact in
the program, sending "power" to the Y1 "coil," energizing the Y1 output and applying 120 volt
AC power to the real motor contactor coil. The parallel Y1 contact will also "close," thus
latching the "circuit" in an energized state:

Figure 4.1(a) – Logic for continuous running of motor when start button is released

Now, if we release the "Start" pushbutton, the normally-open X1 "contact" will return to its
"open" state, but the motor will continue to run because the Y1 seal-in "contact" continues to
provide "continuity" to "power" coil Y1, thus keeping the Y1 output energized:

22
Figure 4.1(b) - to stop the Motor

To stop the motor, we must momentarily press the "Stop" pushbutton, which will energize the
X2 input and "open" the normally-closed "contact," breaking continuity to the Y1 "coil:"

23
Figure 4.1(c) - Input X2 is de-energized

When the "Stop" pushbutton is released, input X2 will de-energize, returning "contact" X2 to its
normal, "closed" state. The motor, however, will not start again until the "Start" pushbutton is
actuated, because the "seal-in" of Y1 has been lost:

4.2 A brief introduction to CoDeSys

4.2.1 What is CoDeSys?

CoDeSys is a complete development environment for your PLC. (CoDeSys stands for
Controlled Development System). CoDeSys puts a simple approach to the powerful IEC
language at the disposal of the PLC programmer. Use of the editors and debugging functions is
based upon the proven development program environments of advanced programming languages
(such as Visual C++)

24
4.2.2 Overview of CoDeSys Functions...

How is project structured?

A project is put into a file named after the project. The first POU (Program Organization Unit)
created in a new project will automatically be named PLC_PRG. The process begins here (in
compliance with the main function in a C program), and other POUs can be accessed from the
same point (programs, function blocks and functions).Once you have defined a Task
Configuration, it is no longer necessary to create a program named PLC_PRG.
There are different kinds of objects in a project: POUs, data types, display elements
(visualizations) and resources. The Object Organizer contains a list of all the objects in your
project.

How do I set up my project?

First you should configure your PLC in order to check the accuracy of the addresses used in the
project. Then you can create the POUs needed to solve your problem. Now you can program the
POUs you need in the desired languages. Once the programming is complete, you can compile
the project and remove errors should there be any.

How can I test my project?

Once all errors have been removed, activate the simulation, log in to the simulated PLC and
"load" your project in the PLC. Now you are in online mode. Now open the window with your
PLC Configuration and test your project for correct sequence. To do this, enter input variables
manually and observe whether outputs are as expected. You can also observe the value sequence
of the local variables in the POUs. In the Watch and Receipt Manager you can configure data
records whose values you wish to examine.

Debugging

25
In case of a programming error you can set breakpoints. If the process stops at such a breakpoint,
you can examine the values of all project variables at this point in time. By working through
sequentially (single step) you can check the logical correctness of your program.

Additional Online Functions

Further debugging functions:
You can set program variables and inputs and outputs at certain values

What is CoDeSys?

CoDeSys is a complete development environment for your PLC. (CoDeSys stands for
Controlled Development System).CoDeSys puts a simple approach to the powerful IEC
language at the disposal of the PLC programmer. Use of the editors and debugging functions is
based upon the proven development program environments of advanced programming languages
(such as Visual C++).

Project

A project contains all of the objects in a PLC program. A project is saved in a file named after
the project. The following objects are included in a project:
POUs (program organization units), data types, visualizations, resources, and libraries.

POU (Program Organization Unit)

Function, function blocks, and programs are POUs which can be supplemented by actions.
Each POU consists of a declaration part and a body. The body is written in one of the IEC
programming languages which include IL, ST, SFC, FBD, LD or CFC.
CoDeSys supports all IEC standard POUs. If you want to use these POUs in your project, you
must include the library standard.lib in your project.
POUs can call up other POUs. However, recursions are not allowed.

26
Visualization

CoDeSys provides visualizations so that you can display your project variables. You can plot
geometric elements off-line with the help of the visualization. In Online mode, these can then
change their form/colour/text output in response to specified variable values.
Visualization can be used as a pure operating interface for a PLC with CoDeSys HMI or as a
Web-Visualization or Target-Visualization running via Internet resp. directly on the PLC.

Supported Languages

CoDeSys supports all languages described by the standard IEC-61131:

Textual Languages:
Instruction List (IL)
Structured Text (ST)

Graphic Languages:
Sequential Function Chart (SFC)
Function Block Diagram (FBD)
The Continuous Function Chart Editor (CFC)
Ladder Diagram (LD)

4.3 Getting started with CoDeSys software

STEP 1:
Install CoDeSys V2.3 version in your computer. This installation is started and can be opened.

Step 2:
All programs>>Messung systems>>CoDeSys V2.3>>homepage opens
Step 3:

27
Starting CoDeSys
Start the CoDeSys programming system with
Start -> Programs -> 3S Software -> CoDeSys V2.3 -> CoDeSys V2.3

Figure 4.3(a) - CoDeSys software

Step 4:
Writing the First Program:
Task:
A running machine is to be observed by a machine operator. Correct running must be confirmed
at specified intervals. If there is no confirmation, a warning is first issued, shortly after which
the machine will be stopped. The machine moves an arm along a rectangular path, and
completed circuits are to be counted.

Creating a new project

Starting is easy. Create a new project with the command File -> New.
• Target Settings
For our first project please select the entry which fits to your runtime system as target in the
combination box ‘Configuration’, e.g. CoDeSys SP for Windows NT Real-time.

28
• The PLC_PRG POU
In the New POU dialog select the language of the POU FBD (Function Block Diagram) and
retain the settings Type Program and Name PLC_PRG.PLC_PRG is a special POU which is
cyclically called and executed by the run-time system in operation.

Step 5: A window appears

Figure 4.3(b) – Target settings

Click ok

Step 6: next window appears automatically as

Figure 4.3(c) – New POU

SELECT
Type of POU = program Language of the POU= LD (ladder diagram)
Click OK

29
 Figure 4.3(d) – File is started

Now you can write the program using certain rules

1. Input  contact  NO(normally open)
 NC (normally closed)

2. Output  coil 
3. To make device on  NO contact
To make device off  NC contact
4. Same input can be used as many times
Same output must be used one time only.
5. Input would not decide output
Output would decide input.
6. Make list of inputs and outputs.

STEP 7: make the project ladder diagram using function INSERT in the task bar and draw the
ladder diagram.

30
STEP 8: Visualization for This:
Create Visualization
In the object organizer at the bottom left select the third tab from the left, named Visualization.
Use the object organizer’s quick menu to call the Add object command.
Give the visualization object a Name, such as Observation.
Draw Visualization Element
Let’s start with the confirmation switch (the rectangle with the text OK in the figure).
Select the symbol for Rectangles from the toolbar.
Press the left hand mouse key in the visualization editor, hold it down, and draw a rectangle with
it. Release the mouse key when it has reached the desired form and size.
• Configure the First Visualization Element
With a double click on the rectangle, the configuration dialog will appear.
In the Contents field of the Text Category write the text OK.
Select the Variables Category, click in the Change Color field and call up the input assistance
with the <F2> function key. Give a double click to the point in the right hand half of the dialog
box and the global variable will appear. Select the Observer variable. The field now contains
.Observer
Start the Target System
• Start the target runtime system. (Please regard that in case of using the runtime system
CoDeSys SP RTE this is only possible on Windows NT 4.0 or Windows 2000. Here you will
get the icon of the Real-time system in the status bar. Click on this with the right mouse button
and choose the command 'Start System'.)
Settings for Establishing the Connection
• A small number of settings must be made before we can establish the connection to the target
computer. For this purpose carry out the menu command Online -> Communication
parameters.
• Select the button new to configure the connection to your target system. Enter an appropriate
name for the connection at the new dialog and select a connection; in case of CoDeSys SP RTE
Shared memory (Kernel).

31
If the target computer is your local computer you can now close the dialog with OK. If the target
computer is not your local computer, you have to change the value 'local host' to the Internet
address or the target name of the target computer. After that also close the communications
parameters dialog with OK.
Start the Project
• The connection to the target computer will be established using the menu command
Online  Login from the CoDeSys development environment and with Online  Run your
program will be started on the target computer. (If you want to work in
Simulation mode, the option 'Online' 'Simulation' must be activated).
• By means of the visualization you can now start the machine and operate the confirmation
switch.

32
 CHAPTER 5
SCADA

5.1 Meaning of SCADA

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 (PLCs), or other commercial hardware modules.

SCADA systems are used not only in industrial processes: e.g. steel making, power generation
(conventional and nuclear) and distribution, chemistry, 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 K: we know of two cases of near to 1 M I/O
channels currently under development.

SCADA systems used to run on DOS, VMS and UNIX; in recent years all SCADA vendors have
moved to NT and some also to Linux.

33
5.2 Architecture

Figure 5.2- Architecture of SCADA

This section describes the common features of the SCADA products that have been evaluated at
Connections CERN in view of their possible application to the control systems of the LHC
detectors [1], [2].

5.2.1 Hardware Architecture

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. The data servers communicate with devices in the field through process
controllers. Process controllers, e.g. PLCs, are connected to the data servers either directly or via
networks or field buses that are proprietary (e.g. Siemens H1), or non-proprietary (e.g. Profibus).
Data servers are connected to each other and to client stations via an Ethernet LAN. The data
servers and client stations are NT platforms but for many products the client stations may also be
W95 machines.

34
5.3 Communications

5.3.1 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.

5.3.2 Access to Devices

The data servers poll the controllers at a user defined polling rate. The polling rate may be
different for different parameters. The controllers pass the requested parameters to the data
servers. Time stamping of the process parameters is typically performed in the controllers and
this time-stamp is taken over by the data server. If the controller and communication protocol
used support unsolicited data transfer then the products will support this too.
The products provide communication drivers for most of the common PLCs and widely used
field-buses, e.g., Mod bus. Of the three field buses that are recommended at CERN, both Profi
bus and World flip are supported but CAN bus often not [3]. 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. The effort required to develop new drivers
is typically in the range of 2-6 weeks depending on the complexity and similarity with existing
drivers, and a driver development toolkit is provided for this.

35
5.4 Interfacing

The provision of OPC client functionality for SCADA to access devices in an open and standard
manner is developing. There still seems to be a lack of devices/controllers, which provide OPC
server software, but this improves rapidly as most of the producers of controllers are actively
involved in the development of this standard. OPC has been evaluated by the CERN-IT-CO
group.

The products also provide

 An Open Data Base Connectivity (ODBC) interface to the data in the archive/logs, but
not to the configuration database,
 An ASCII import/export facility for configuration data,
 A library of APIs supporting C, C++, and Visual Basic (VB) to access data in the RTDB,
logs and archive. 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).
The configuration data are stored in a database that is logically centralized but physically
distributed and that is generally of a proprietary format. For performance reasons, the RTDB
resides in the memory of the servers and is also of 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.

5.4.1 Scalability

Scalability is understood as the possibility to extend the SCADA based control system by adding
more process variables, more specialized servers (e.g. for alarm handling) or more clients. The
products achieve scalability by having multiple data servers connected to multiple controllers.

36
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).

5.4.3 Redundancy

The products often have built in software redundancy at a server level, which is normally
transparent to the user. Many of the products also provide more complete redundancy solutions if
required.

5.5 Functionality

5.5.1 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.

5.5.2 MMI

The products support multiple screens, which can contain combinations of synoptic diagrams
and text. They also support the concept of a "generic" graphical object with links to process
variables. These objects can be "dragged and dropped" from a library and included into a
synoptic diagram. 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, many of which
would however not be applicable to the type of applications encountered in the experimental
physics community. Standard windows editing facilities are provided: zooming, re-sizing,
scrolling... On-line configuration and customization of the MMI is possible for users with the

37
appropriate privileges. Links can be created between display pages to navigate from one view to
another.

5.5.3 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

5.6 Alarm Handling

Alarm handling is based on limit and status checking and performed in the data servers. More
complicated expressions (using arithmetic or logical expressions) can be developed by creating
derived parameters on which status or limit checking is then performed. The alarms are logically
handled centrally, i.e., the information only exists in one place and all users see the same status
(e.g., the acknowledgement), and multiple alarm priority levels (in general many more than such
levels) are supported.
It is generally possible to group alarms and to handle these as an entity (typically filtering on
group or acknowledgement of all alarms in a group). Furthermore, 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. However,
relationships between alarms cannot generally be defined in a straightforward manner. E-mails
can be generated or predefined actions automatically executed in response to alarm conditions.

5.7 Logging/Archiving

38
The terms logging and archiving are often used to describe the same facility. However, 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, i.e., once a certain file size, time period or number of points is
reached the data is overwritten. Logging of data can be performed at a set frequency, or only
initiated if the value changes or when a specific predefined event occurs. 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. The logging of user actions is in general performed together with either a
user ID or station ID. There is often also a VCR facility to play back archived data.

5.8 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, a "cut and paste" capability is in
general not provided. Facilities exist to be able to automatically generate, print and archive
reports.

5.9 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. In general, one
can load a particular display, send an Email, run a user defined application or script and write to
the RTDB. The concept of recipes is supported, whereby a particular system configuration can
be saved to a file and then re-loaded at a later date.

39
 CHAPTER 6
Application & Development in SCADA

6.1 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 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.

The products also provide an ASCII Export/Import facility for the configuration data (parameter
definitions), which enables large numbers of parameters to be configured in a more efficient
manner using an external editor such as Excel and then importing the data into the configuration
database.

However, many of the PC tools now have a Windows Explorer type development studio. The
developer then works with a number of folders, which each contains a different aspect of the
configuration, including the graphics. The facilities provided by the products for configuring
very large numbers of parameters are not very strong.

However, this has not really been an issue so far for most of the products to-date, as large
applications are typically about 50K I/O points and database population from within an ASCII
editor such as Excel is still a workable option. On-line modifications to the configuration
database and the graphics are generally possible with the appropriate level of privileges.

40
6.2 Development Tools

The following development tools are provided as standard:

 A 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.
 A data base 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.
 A scripting language
 An Application Program Interface (API) supporting C, C++, VB

6.3 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.
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.

41
6.4 Engineering

Whilst one should rightly anticipate significant development and maintenance savings by
adopting a SCADA product for the implementation of a control system, it does not mean a "no
effort" operation. The need for proper engineering cannot be sufficiently emphasized to reduce
development effort and to reach a system that complies with the requirements, that is economical
in development and maintenance and that is reliable and robust. Examples of engineering
activities specific to the use of a SCADA system are the definition of:
 a library of objects (PLC, device, subsystem) complete with standard object behavior
(script, sequences, ...), graphical interface and associated scripts for animation,
 templates for different types of "panels", e.g. alarms,
 instructions on how to control e.g. a device ...,
 a mechanism to prevent conflicting controls (if not provided with the SCADA), alarm
levels, behavior to be adopted in case of specific alarms.

6.5 Potential benefits of SCADA

The benefits one can expect from adopting a SCADA system for the control of experimental
physics facilities can be summarized as follows:
 A rich functionality and extensive development facilities. The amount of effort invested
in SCADA product amounts to 50 to 100 p-years!
 The amount of specific development that needs to be performed by the end-user is
limited, especially with suitable engineering.
 Reliability and robustness. These systems are used for mission critical industrial
processes where reliability and performance are paramount. In addition, specific
development is performed within a well-established framework that enhances reliability
and robustness.
 Technical support and maintenance by the vendor.

42
 CHAPTER 7
Project examples

7.1 PROBLEM1: Lighting 3 bulbs using 2 switches.

1. Using button 1 bulb 1 &2 lights up
2. Using button 2 bulb 2 lights up
3. Using button 1 & 2 bulb 3 lights up

SOLUTION:
Inputs: I1, I2
Outputs: Q1, Q2, Q3

Figure 7.1(a) - programming on CoDeSys

43
VISUALIZATION:

Figure 7.1(b)-visualization

44
 7.2 PROBLEM 2: 3 inputs 1 output, any two inputs are used to light up the output.
1. Input 1 &2 light up output
2. Input 2 &3 light up output
3. Input 3 &1 light up output

SOLUTION:
Input: I1, I2, I3
Output: Q1

Figure 7.2(a) Programming on CoDeSys

VISUALIZATION:

Figure 7.2(b) -visualization

45
7.3 PROBLEM 3: Auto Door Lamp.
An input switch and the closing of the door control the switching on/off of an lamp.

SOLUTION:
Input: I1, I2
Output: Q1

Figure 7.3(a) - Programming on CoDeSys

VISUALIZATION:

Figure 7.3(b) - visualization

46
7.4 PROBLEM 4: Auto Drill Application:

Drilling operation which is to be done as shown in a working slide show program

Figure 7.4(a) - programming on CoDeSys

47
VISUALIZATION:

Figure 7.4(b) - visualization

NOTE: I PRACTISED OTHER EXAMPLES AS WELL BUT IT IS VERY DIFFICULT TO

SHOW SLIDE SHOW PRIDICTING EXAMPLE. THE LADDER LOGIC AND THE
VISUALISATIONS SO FOR EASE I HAVE ILLUSTRATED ONLY FEW OF THE PROJECT
WORK EXAMPLES

48
49
 CONCLUSION

During my Training I learnt a lot, due to the result of hard working of my guides & co-operation
of my parents. It was an interesting experience to know the spirit of industriousness, human
relationship, punctuality & hard work. The period of six months training was really a great
experience in industries field.
I also learnt how to co-ordinate with the colleagues & also increased my personal skill it will be
helpful a lot in my future. It has given a lot of my knowledge & is an essential part of technical
education programmed. As it is a new technology based training in automation and design of
logics, we were given a brief study of the PLC, the learning of languages ladder logic, building
the PLC program of the provided slide show was a good experience and then working with the
wiring diagram and the wiring circuits using machinery like the switches, push button, the
stepper motor. We were given an introduction, working about the PLC salient features, general
description, switch, relays, ladder logic, wiring of PLC of Siemens and Allen-Bradley.
My training section mainly included knowing about the basics of PLC, study of controllers,
inputs, working, logic building, installing, ladder logic and simple wiring. Overall it was a great
learning project and I also express my sincere thanks to all the other engineers and staff members
of the institute for their co-operation and valuable guidance for completion of the project.
It was great pleasure learning and we were given a lot of knowledge & this training was an
essential part of technical education programmed. On completion of this six months training I am
very well aware about PLC, its working, implementation and building of the ladder logic with its
visualization and programming of PLC.
SCADA is used for the constructive working not for the destructive work using a SCADA
system for their controls ensures a common framework not only for the development of the
specific applications but also for operating the detectors. Operators experience the same "look
and feel" whatever part of the experiment they control. However, this aspect also depends to a
significant extent on proper engineering.

x
 LIMITATIONS

The training we achieved during last six months made us industry ready; however we observed
some of its limitations. These are listed below:
 Time consumptive.
 Costly.
 No modular adds on.
 Can’t evolve with technology.
 Can’t streamline functionality.

PRACTICAL SCOPE OF TRAINING

The application systems in industries require a person to monitor control instruments. This is
where plc consisting of programmable micro controllers that uses a specialized computer
language. Normally, the program is written then downloaded to plc using cable connection
which results in storage of program in the volatile memory. Since they are designed for usage
during real time, it can not only endure harsh environment.
Industrial automation is a part of the engineering which applied on basis in our day to day life.
Also in any company whether it is an IT firm or non-IT firm industrial automation is always in
huge demand. The latest technologies in industrial automation include PLC & SCADA which is
highly demand in job market scenario.
It controls an industrial system and operates the entire factory or water treatment plans.
In our routine life everything starting from the finger print recognisation machine, lifts, escators,
facial recognisation machine the PLC & SCADA technology is used.
In this technology gadgets are reprogrammed to do certain tasks. The appropriate reason for
applying automation is to increase productivity and quality that possible with current human
labour levels so as to achieve. Automation is also used in service sector.

xi
 BIBLIOGRAPHY

References:
 Automating Manufacturing Systems with PLCs by Hugh jack
 Asfahl, C.R., “Robots and Manufacturing Automation”, second edition.
 Batten, G.L., Programmable Controllers: Hardware, Software, and Applications,
Second Edition, McGraw-Hill, 1994.
 Bertrand, R.M., “Programmable Controller Circuits”, Delmar, 1996.
 Bryan, L.A., Bryan, E.A., Programmable Controllers, Industrial Text and Video-
company, 1997.
 Carrow, R.A., “Soft Logic: A Guide to Using a PC As a Program Controller”,
McGraw Hill, 1997.
 Lewis, R.W., “Programming Industrial Control Systems using IES1131-3”.

Websites:

 www.definition-of.com/plc
 www.allaboutcircuits.com
 Google search engine.
 www.control-systems-principles.co.uk/.../programmable-logic-control.pdf
 www.automationdirect.com/static/specs/whatisaplc.pdf

xii