FORMAT FOR PREPARATION OF SEMINAR REPORT

a) Arrangement of contents:
1. Title Page
2. Certificate
3. Declaration
4. Acknowledgement
5. Abstract
6. Table of Contents
7. List of Tables
8. List of Figures
9. Abbreviations
10. Chapters: Chapters should be in following sequence:
 Chapter 1: Introduction
 Chapter 2: Literature Survey
 Chapter 3: Block Diagram / Description (Take Printout of 4 slides on each page)
 Chapter 4: Applications /Advantages-Disadvantages
 Chapter 5: Conclusion
11. References: Should be in IEEE Format

Note: 1) Chapter pages should include “Name of Seminar Topic” as header and “YSPM’s Yashoda
Technical Campus, Department of E&TC” as the footer with left aligned.
2) Page numbers should be at the bottom of the page with right alignment.

b) Typing Instructions:

1. The Seminar report must be submitted to the department duly signed by the Supervisor. Students should
also submit the soft copy on CD in PDF format to the Supervisor.
2. The length of the report may be up to 70 pages.
3. The Seminar report shall be computer typed (English- British, Font -Times Roman, Size-12 point) and
printed on A4 size paper.
4. The Seminar report shall be hard bound with cover page in black color. The name of the students, degree,
month and year of submission, name of the university including institute name shall be printed in golden
letters on the cover page [Refer sample sheet]
5. The Seminar report shall be typed with 1.5 line spacing with a margin 1.5 inches on the left, 1 inch on the
top, bottom & right. Every page in the Seminar report report must be numbered. The page numbering,
starting from acknowledgements and till the beginning of the introductory chapter, should be printed in
small Roman numbers, i.e, i, ii, iii, iv...... The page number of the first page of each chapter should not be
printed (but must be accounted for). All page numbers from the second page of each chapter should be
printed using Arabic numerals, i.e. 2,3,4,5... All printed page numbers should be located at the bottom
centre of the page.
6. In the Seminar report report, the Title page [Refer sample sheet] should be given first then the Certificate
by the supervisor(s) in sequence, followed by an acknowledgement and abstract of the report (not
exceeding one page) and so on.
7. Abstract should be straight to the point; not too descriptive but fully informative. The following things
should appear in the abstract. (a) the problem addressed, (b) its importance/novelty, (c) the approach
adopted for solving the problem, highlighting novelty, if any, (d) the major results obtained, (e) and the
major conclusion. The abstract does not have to be an entire summary of the Seminar report, but rather a
concise summary of the scope and results of the Seminar report. It should inform a reader whether to read
or not the full text, and also give a precise idea on what has been attempted. An abstract should be short,
and limited to 1 page. Include key words.
8. The table of contents should list all material following it as well as any material which precedes it. The
title page, Certificate may not be included in the Table of Contents, but the page numbers of which will be
in lower case Roman numbers. One and a half spacing should be adopted for typing the matter under this
head.
9. The list of figures should use exactly the same captions as they appear below the figures in the text. One
and a half spacing should be adopted for typing the matter under this head.
10. The list of abbreviation should be typed with one and a half line spacing. Standard symbols, abbreviation
etc should be used.
11. Seminar report consists of various chapters.
Each chapter should be given an appropriate title. Tables & figures in a chapter should be placed in
the immediate vicinity of the reference where they are cited. Footnotes should be used sparingly.
They should be typed single space and placed directly underneath in the very same page, which
refers to the material they annotate. Conclusion must not exceed more than two pages. Future scope
also must not exceed one page.
13. Appendices are provided to give supplementary information, which is included in the main text may serve
as a distraction and cloud the central theme.

i) Appendices should be numbered using Arabic numerals, e.g. Appendix 1, Appendix 2, etc.
 ii) Appendices, Tables and References appearing in appendices should be numbered and referred to at
appropriate places just as in the case of chapters.
iii) Appendices shall carry the title of the work reported and the same title shall be made in the contents
page also.

14. The listing of references should be typed below the heading “REFERENCES” in chronological order of year of
publication in single spacing left – justified.. The name of the author (s) should be immediately followed by the
year and other details.
A typical illustrative list given below relates to the citation example quoted above.

REFERENCES:

1. Anderson, J.D. (1995) Computational Fluid Dynamics. McGraw Hill, Singapore 1995.

2. Barnard, R.W. and Kellogg, C. (1980) ‘Applications of Convolution Operators to Problems in Univalent
Function Theory’, Michigan Mach, J., Vol.27, pp.81–94.

3. Shin, K.G. and Mckay, N.D. (1984) ‘Open Loop Minimum Time Control of Mechanical Manipulations and
its Applications’, Proc.Amer.Contr.Conf., San Diego, CA, pp. 1231-1236.

4. Smith, R., (2002), ―Conformal Lubricated Contact of Cylindrical Surfaces Involved

in a Non-Steady Motion,‖ from web site http://www.cas.phys.unm.edu/rsmith/homepage.html accessed on
12/08/2007.
 “PROGRAMABLE LOGIC CONTROLLER”
A SEMINAR REPORT
Submitted in partial fulfillment for the award of the degree of
BACHELOR OF TECHNOLOGY
Submitted to

Dr.Babasaheb Ambedkar Technological University,Lonere.

Submitted By

JADHAV ABHISHEK RAVINDRA (23067571372505)

Under the Guidance of

Mrs.K.V.Idate

Electronics & Telecommunication Engineering

YSPM’s Yashoda Technical Campus
Faculty of Engineering
Wadhe, Satara-415011
2023- 24
 CERTIFICATE
(Times New Roman, Size 16, Bold and Centre aligned)

(Times New Roman, Size 12)

This is to certify that the Seminar entitled “ Programable Logic Controlle“ submitted by Jadhav Abhishek

Ravindra(23067571372505) is a record of the bonafide work carried out by him / her, under my guidance, and it is

approved for the partial fulfillment of requirement of Dr. Babasaheb Ambedkar Technological University, Lonere

for the award of the degree Bachelor of Technology (Electronics and Telecommunication).

Mrs.K.V.Idate Prof.Santosh Itraj Prof.Badadapure.P.R

Guide Head of Department Principal

Name of dept Name of dept YSPM’s YTC,Satara

(External Examiner)

Place: Satara

Date:
 Declaration by Student(s)

This is to declare that this report has been written by me/us. No part of the report is plagiarized
from other sources. All information included from other sources has been duly acknowledged.
I/We aver that if any part of the report is found to be plagiarized, I/we are shall take full
responsibility for it.

<<Signature of Student>>

<<Jadhav Abhishek Ravindra>>

<<Exam Seat No.: 23067571372505>>

Place

Date

Note: Declaration for individual copy

 Declaration by Student(s)

This is to declare that this report has been written by me/us. No part of the report is plagiarized
from other sources. All information included from other sources have been duly acknowledged.
I/We aver that if any part of the report is found to be plagiarized, I/we are shall take full
responsibility for it.

Signature of Students

1.

Place

Date

Note: Declaration for Department copy

 ACKNOWLEDGEMENT
It is our privilege to acknowledge my deep sense of gratitude to my guide Mrs.K.V.Idate. in E&TC Engineering at
Yashoda Technical Campus. Satara for her valuable suggestions and guidance throughout our degree course and
the timely help given to us in completion of our Seminar work. We are thankful to Dr. Badadapure P. R. Principal,
Yashoda Technical Campus, Satara and Prof.Santosh Itraj. Head of General Science and Humanities for their kind
co-operation & morale support. Finally, we wish to express our sincere thanks to all the staff members of Yashoda
Technical Campus, Satara for their direct and indirect help
 ABSTRACT
The programmable Logic Controller (PLC) is the central controlling unit in the industry or a process. The effective
operation of the process and safety considerations if programmed appropriately can meet the required objectives.
The present technical paper briefly distinguishes the present automation systems and the past technologies to
identify and explore the capabilities of PLCs for any process. The relay logic and contactor logics (RLC) were
practiced in the olden days which include the human intervention and errors. The advent and application of
microprocessors, microcontrollers and new specific tools such as PLCs, Supervisory control and data acquisition
(SCADA) and Distributed control systems (DCS) have increased productivity, accuracy, precision and efficiency.
These systems reduced human intervention and increased the flexibility in the process control. The keyword
automation clearly states that the working of a process or repetition in an efficient manner by incorporating
mechanisms and control sequences in the proper order several times with acceptable deviations in the output of the
process
 CONTENTS

(Times New Roman, Size 14 Bold and Centre aligned)

Acknowledgement i
Abstract ii
List of Tables iii
List of Figures iv
Abbreviations v
Chapter Contents Page No.

1 Introduction 1
1.1
1.1.1

Note: Hide the border of above table

 LIST OF TABLES

Table Title Page No.

Note: Hide the border of above table

 LIST OF FIGURES

Figure Title Page No.

Note: Hide the border of above table

 ABBREVIATIONS

TDM Time division multiplexing

Note: Abbreviations should be listed in order of appearance.

Hide the border of above table

 CHAPTER 1
INTRODUCION
A Programmable Logic Controller (PLC) is a specialized industrial computer control system used to replace banks
of electromagnetic relays in industrial process control via continuously monitoring the state of input devices and
makes decisions based upon custom program to control the state of output devices. The PLC is also known as a
programmable controller (PC). The tile "PC" for programmable controller could be confused in common usage
with "PC" used to mean personal computer. To avoid this confusion, it is generally referred as programmable
controller or programmable logic controller or PLC.The programmable logic controller is like a heavy-duty
computer system designed for machine control. Like a general-purpose computer, the PLC is based on digital logic
and can be field-programmed. The programming language is a bit different because the purpose of the PLC is to
control machines. The PLC is used to time and sequence functions that might be required in assembly lines, robots,
and chemical processing. It is designed to deal with the harsh conditions of the industrial environment. Some of the
physical environment problems could include vibration and shock, dirt and vapors, and temperature extremes. The
PLC commonly has to interface with a wide variety of both input and output devices. Some input devices include
limit and pressure switches, temperature and optical sensors, and analog- to digital converters (ADCs). Some
output devices valves, motors and cylinders, and Digital-to Analog converts (DAC).

Before the advent of solid-state logic circuits, logical control systems were designed and built exclusively around
electromechanical relays. Relays are far from obsolete in modern design, but have been replaced in many of their
former roles as logic-level control devices, relegated most often to those applications demanding high current
and/or high voltage switching. Systems and processes requiring "on/off" control abound in modern commerce and
industry, but such control systems are rarely built from either electromechanical relays or discrete logic gates.
Instead, digital computers fill the need, which may be programmed to do a variety of logical functions.

In the late 1960's an American company named Bedford Associates released a computing device they called the
MODICON. As an acronym, it meant Modular Digital Controller, and later became the name of a company
division devoted to the design, manufacture, and sale of these special-purpose control computers. Other
engineering firms developed their own versions of this device, and it eventually came to be known in non-
proprietary terms as a PLC, or Programmable Logic Controller.The leading PLC Manufacturers are Siemens,
Schneider, Allen Bradley, Mitsubishi, Omron, ABB, Panasonic, GE Fanuc, LG, Fatek, Delta etc.The purpose of a
PLC was to directly replace electromechanical relays as logic elements, substituting instead a solid-state digital
computer with a stored program, able to emulate the interconnection of many relays to perform certain logical
tasks.

A PLC has many "input" terminals, through which it interprets "high" and "low" logical states from sensors and
switches. It also has many output terminals, through which it outputs "high" and "low" signals to power lights,
solenoids, contactors, small motors, and other devices lending themselves to on/off control. In an effort to make
PLC easy to program, their programming language was designed to resemble ladder logic diagrams. Thus, an
industrial electrician or electrical engineer accustomed to reading ladder logic schematics would feel comfortable
programming a PLC to perform the same control functions.

PLC are industrial computers, and as such their input and output signals are typically 230 volts AC, just like the
electromechanical control relays they were designed to replace. Although some PLC has the ability to input
andoutput low-level DC voltage signals of the magnitude used in logic gate circuits, this is the exception and not
the rule.
 CHAPTER 2
LITERATURE SURVEY
Literature Survey 1

By – Michael R. Foster , 2010

Reviewing the educational literature for descriptions of PLC projects (see Table 1), it was rare to find papers where
all authors were from a mechanical engineering department.25 The remaining articles include or are solely written
by individuals from electrical/computer engineering or engineering technology departments. The lack of PLC
projects indicates that very few programs are taking advantage of a versatile tool, where as papers involving
collaborative inter-departmental efforts demonstrate the willingness or need to capitalize on commonalities
between disciplines.29The collaborations also highlight the robust feature set that PLCs have gained since their
replacement of cumbersome electro-mechanical systems 40 years ago. The projects listed in Table 1 indicate a
variety of non-continuous and continuous-based control implementation. In particular, one laboratory contains an
array of experiments with electrical, mechanical ,pneumatic, and hydraulic systems.11 Another program provides a
thermal process control lab.4 Note that very similar projects are offered from both mechanical and electrical
engineering departments, yet the outcome of each project is appropriate to the area. For example, students in both
areas of engineering investigate the control of DC motors6,25 and conveyor.

Literature Survey 2

By - Robert Melendy , 2010

From the authors’ experiences and the examples given by colleagues in teaching ladder logic programming,
students struggle with how to structure a ladder diagram from a given problem statement. Specific approaches have
been offered in the literature as ways to acquire effective programming skills. James Rehg describes two
approaches to ladder logic programming: empirical and pseudo structured.24 Noting that the empirical approach is
well suited for small applications, he details a pseudo structured approach, called sequential function charts. This
process requires extended planning and development time of the programming but significantly reduces the
implementation and troubleshooting of programming problems. Another approach to ladder logic programming is
“I/O mapping,” developed by Durward Sobek at Montana State University.27 At the start of the design sequence,
each system input and output are listed or diagrammed separately on a page. Links are then drawn from the inputs
to any output they effect. Finally, a Boolean expression is developed for each output, which enables an easier
translation into programming rungs. The author presents some quantitative data indicating that both quality and
efficiency in the problem solving process improved
CHAPTER 3
DESCRIPTION