SCHOOL OF

ELECTRICAL ENGINEERING

Lab Manual
Linear Control Systems
EE-413

SUBMITTED TO:

SUBMITTED BY:

REG NO:

CLASS: BEEE

SEMESTER: 6th

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

1
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 I. Laboratory Safety Policies

1. General laboratory safety

 Never eat or drink while working in the laboratory.
 Read the labels carefully.
 Do not use any equipment unless you are trained and approved as a user by supervisor.
 Wear safety glass or face shield when using any hazardous materials and /or equipment.
 Wear gloves when using any hazardous or toxic agent.
 Never do unauthorized experiments.
 Never work alone in laboratory.
 Keep your lab space clean and organized.
 Do not leave an on-going experiment unattended.
 Never taste anything. Never pipette by mouth; use a bulb.
 Never use open flames in laboratory unless instructed by T A.
 Check your glass ware for cracks and chips each time you use it. Cracks could cause
the glassware to fail during use and cause serious injury to you or lab mates.

2. Clothing
 When handling dangerous substances, wear gloves, laboratory coats, and safety shield
or glasses. Shorts and sandals should not be worn in the lab at any time. Shoes are
required when working on the machine shops
 If you have long hair and loose clothes then make sure that it is tied back or confined.
 Keep the work area clear of all materials except those needed for your work.

3. Disposal
 Students are responsible for the proper disposal of used material if any in
appropriate containers.

4. Equipment Failure
 If a piece of equipment face while being used, report it immediately to lab engineer
/ assistant. Never try to fix the problem yourself because you could harm yourself
and others.
 If leaving a lab unattended, turn off all ignition sources and lock the doors.
 Clean up your work area before leaving.
 Wash hands before leaving the lab and before eating.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

2
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 5. Electricity
 Obtain permission by the safety coordinator before operating any high voltage
equipment.
 Maintain an unobstructed access to all electrical panels.
 Avoid using extension cords whenever possible.
 Never, ever modify or otherwise change any high voltage equipment.
 Before attracting the power supply to your setup make sure there no ‘’live’’ wires
which can be touched.
 When attaching a high voltage power supply ALWAYS switch off the supply.

6. Fire
 If a person’s clothing catches on fire, he/she needs help.
 Prevent him/her from running.
 Make him/her lie down and smother the flame by rolling, wrapping with lab coats,
blankets, towels, etc.
 Never turn a carbon dioxide extinguisher on a person.
 If a fire breaks out, (if time allows) turn off all burners and remove solvents, place
the chemical and equipment safely to the nearest possible table/bench, exit the
building calmly.
 If you do not use the fire extinguisher, leave the room immediately to a safer place
possible outside. There are carbon dioxide extinguisher in the building and the
position and operation of these should be known.
 Point the extinguisher at the base of the flames.
 Very small fires can be put out with a damp towel by smothering.
 Only after the safety of all is assured the matter of the extinguisher the fire is
considered.

Because a few seconds delay can result in very serious injury, Laboratory staff will
guide you on what to do and how to exit during the case of such an emergency.

8. In Case of emergency

 Report the location of the emergency; give your name, telephone number, and
building and floor number.
 Report the nature of the emergency whether an explosion has occurred and whether
there has been a chemical or electrical fire.

RESCUE: 1122

Police Emergency Control Room: 041-9200264

Army Control Room: 1135

Administrator: 041-8750971 (Ext. 327)

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

3
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 II. Safety Undertaking

I HAVE READ ALL OF THE ABOVE, AND I AGREE TO CONFORM TO ITS

CONTENTS.

Name: Course:

Student Reg: Section:

Signature: Room:

Date:

Lab instructor:

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

4
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Sr. Title of Experiment Marks Sign
No. Performance Lab
(20) Report(10)
1

2
3
4
5
6
7
8

9
10
11
12
13
14

15
16

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

5
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 III. Grading Policy
Lab Performance 20%
Lab Report 10%
Lab Viva 50%
Lab Written Test 20%

Rubrics
Lab Performance (Continuous Assessment) / Performance Test
Performance Exemplary Satisfactory Developing Unsatisfactory
indicator (10-9) (8-6) (5-3) (2-0)
Ability to Fully Has very good Has some Has poor
conduct understands understanding of understanding of understanding of
Experiment the software the software tools the software the software tools
tools including including its tools including including its
its purpose and purpose and quite its purpose and purpose and
quite able to able to conduct able to conduct unable to conduct
conduct the experiment with experiment with experiment on his
entire some help from a lot of help own; lab instructor
experiment lab instructor from lab provides help in
with negligible instructor almost every step
help from lab
instructor
Implementati Has an Has good skill to Has weak skill to Has poor skill to
ons and excellent skill draw UML draw UML draw UML
Results to draw UML diagram and able diagram and able diagram, unable to
diagrams. to draw the to draw UML draw UML
Always able to acceptable UML diagram in quit diagram and has
draw the UML diagrams most of less quality no ability to
for given the time and manner. Output identify and
problems and produce output results are not differentiate
produce a high diagram for a that clear. between different
quality given problem types UML
diagrams with diagrams basic
desired output blocks.
results

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

6
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 Lab Report
Sr. Performance Exemplary Satisfactory Developing Unsatisfactory
No. Indicator (5) (4-3) (2-1) (0)

1. Information is Information is Information is Unable to submit

presented in a presented in presented in quite the lab report.
logical somewhat logical less continuity and
interesting manner. All sections less logical
Organization/ way, which is are in a correct order manner. Sections
Structure easy to follow. as directed and are not in a proper
All sections submitted on a time. order as directed
are in a correct and unable to
order and follow the
submitted on submission
time. deadline.
2. Data Result and Result and Result and Unable to submit
Presentation conclusion are conclusion are stated conclusion are the lab report.
stated and and reflect acceptable stated but reflect
reflect knowledge of three little of three
complete experiment Each and experiment. Code
knowledge of every line of the code is not properly
three somehow explained explained with
experiment. with comments and comments.
Each and every outputs/ screen shots
line of the code are attached.
fully explained
with comments
and outputs/
screen shots
are attached.

(Lab Viva)

Sr.# Performance Exemplary Satisfactory Unsatisfactory

Indicator (10-7) (6-3) (2-0)
1.
Responsiveness to Responds well, Generally Non-responsive
Questions/Accuracy quick and very responsive and
accurate all the accurate most
time. of the times.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

7
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
2. Level of Demonstration of At least with No grasp of
understanding of full knowledge of content and able information. Clearly
the learned skill the subject with to elaborate and no knowledge of
explanations and explain to some subject matter. No
elaboration degree. questions are
answered. No
interpretation made
3. Understanding of Has an excellent Has good Has poor ability to
different types of ability to identify ability to identify and
UML diagrams and differentiate identify and differentiate between
between different differentiate different types of
types of UML between UML diagrams.
diagrams. different types
of UML
diagrams.
4. Fulfill team Role’s Performs all duties Performs nearly Does not perform
Duties of assigned team all duties any duties of
role. Always does .Usually does assigned team role.
the assigned work the assigned Always relies on
without having to work-rarely others to do the work
be reminded needs
reminding

5. Confidence Is very confident Is confident to Doesn’t have

and explains the some extent confidence to
details properly. with quite less explain and deliver
Proper eye contact eye contact and topic properly. No
is maintained all presentational eye contact and
the time with gestures. presentational
proper gestures used.
presentational
gestures.

Lab Written Test

Sr. Performance Exemplary Satisfactory Developing Unsatisfactory
No. Indicator (10-9) (8-6) (5-3) (2-0)

1. Level of Demonstration At ease with Only basic No grasp of

Understanding of full content and concept are information.
knowledge of able to demonstrated Clearly no
the subject elaborate and and interpreted. knowledge of
with explain to some subject matter. No
explanations degree. question are
and elaborate. answered. No

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

8
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 interpretation
made.
2. Solution Student Student shows Student tries to Student does not
answer the some prior answer the know how to
question knowledge and question but answer the
correctly and may use does not show question.
completely. terminology to evidence of
Student answer the any previous
incorporates question. knowledge to
information Student does assist in
from the text not use answering.
or lab notes appropriate Student may
into the information reveal
answer. from the text or misconceptions
lab notes to about concepts.
answer the
question.

IV. Level of Inquiry

Level Problem/Question Procedure/Method Solution

0 Provided to student Provided to student Provided to student

1 Provided to student Provided to student Constructed by student

2 Provided to student Constructed by student Constructed by student

3 Constructed by student Constructed by student Constructed by student

Level of Description
Inquiry
0 The problem, procedure, and methods to solution are provided to the student. The
student performs the experiment and verifies the result with this manual.

1 The problem and procedure are provided to the student. The student interpret the
data in order to propose viable solutions.

2 The problem is provided to the student. The student develops a procedure for
investigating the problem decides what together and interprets the data in order to
propose viable solutions.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

9
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 3 A raw phenomenon is provided to the student. The student chooses the problem
to explore develop a procedure for investigating the problem decides what
together and interprets the data in order to propose viable solutions.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

10
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 Program: BEE- Electrical Engineering Semester: VII
Subject: EE-418 Software Engineering
V. List of Experiments
Sr. No. Title of Experiment Level of CLO
Inquiry
Experiment 1 Difference between IBM Rational Rose and 0 CLO1
Microsoft Visio
Experiment 2 Software Development Lifecycle (SDLC) 1 CLO1

Experiment 3 Use cases Diagram of Medical Health Care System 1 CLO1

Experiment 4 Data Flow Diagram of Banking System 1 CLO1

Experiment 5 Data Flow Diagram of Airlines Reservation System 1 CLO1

Experiment 6 Data Flow Diagram of Designing Library System 1 CLO1

Experiment 7 Data Flow Diagram of Hospital Management 1 CLO1

System
Experiment 8 Data Flow Diagram of Employee Management 1 CLO1
Application
Experiment 9 Activity Diagram for Access Camera surveillance 2 CLO1

Experiment 10 Class Diagram of Floor Plan 2 CLO1

Experiment 11 Sequence Diagram of Safe Home Security 2 CLO1

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

11
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Experiment 12 State Diagram of Microwave oven system 2 CLO1

Experiment 13 Path Coverage Testing and Control flow graphs 1 CLO1

Experiment 14 Content Management Software Systems for 2 CLO2

Businesses
Experiment 15 Testing automation tools for software testing 2 CLO2

Experiment 16 Software Version Control 2 CLO2

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

12
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 Lab Course Learning Outcomes
Course Title: Linear Control Systems (EE-413)
Laboratory: Control Systems & Simulation Lab
Instructor: Engr. Umar Farooq
Designation: Lab Engineer
Email: umar.farooq.lab@tuf.edu.pk
Phone: 0092-333-8978033

Course Objective:

This Laboratory course is designed to introduce the analysis of linear control systems. This
will permit an engineer to exploit time domain and frequency domain tools. It provides
knowledge to the students to use the basic components of control systems, various time domain
and frequency domain tools for analysis. Also prepare students to design linear control systems.
It provides methods to analyze the stability of systems from transfer function forms and concept
of state variable analysis.

CLO1: (P1)

Practically analyze the analog control equipment, DC motor module, interfacing module and the Visual
Control Laboratory (VCL) software. Also have practical experience of stability control using different
PID setting.

CLO2: (P2)

Measure and observe the time response, frequency response, parameters and the characteristics
of plant model by using different input functions. Bode plot analysis and frequency analysis of
first order lag and second order control system.

CLO3: (P3)

Present experiment results in a written report.

Mapping of Course Learning Outcomes (CLOs) to Program Learning Outcomes (PLOs) /

Graduate attributes.

Course PLOs PLO1 PLO2 PLO3 PLO4 PLO5 PLO6 PLO7 PLO8 PLO9 PLO10 PLO11 PLO12

Code
CLOs

CLO1 
CLO2 

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

13
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
PLO1: Engineering Knowledge PLO7: Environment and Sustainability

PLO2: Problem Analysis PLO8: Ethics

PLO3: Design / Development of Solutions PLO9: Individual and Team Work

PLO4: Investigation PLO10: Communication

PLO5: Modern Tool Usage PLO11: Project Management

PLO6: The Engineer and Society PLO12: Lifelong Learning

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

14
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Program: BEE- Electrical Engineering Semester: VII
Subject: EE-418 Software Engineering Date: ………….

Lab Report 1: Difference between IBM Rational Rose and Microsoft

Visio
Objectives:
You will learn following:

 Microsoft Visio.
 Rational Rose.
 Difference between MS Visio and Rational Rose.

Name: ……………………………..

Rubrics
Performance Lab Report
Description Total Marks Description Total Marks
Marks Obtained Marks Obtained
Ability to 10 Organization/ 5
conduct Structure
Experiment
Implementations 10 Data 5
and Results Presentation
Total Marks Obtained

Remarks (if any): …………………………………….

Name & Signature of faculty: ………………………

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

15
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Theory:
MICROSOFT VISIO.
Microsoft Office Visio is a diagramming and vector graphics application and is part of
the Microsoft Office family. The product was first introduced in 1992, made by the Shapeware
Corporation. It was acquired by Microsoft in 2000.

Microsoft made Visio 2013 for Windows available in two editions:

1. Standard
2. Professional.
The Standard and Professional editions share the same interface, but the Professional edition
has additional templates for more advanced diagrams and layouts, as well as capabilities
intended to make it easy for users to connect their diagrams to data sources and to display their
data graphically. The Professional edition features three additional diagram types, as well as
intelligent rules, validation, and sub process (diagram breakdown).

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

16
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 What is the use of Microsoft Visio?
Microsoft Visio can be used to create simple or complicated diagrams. It offers a wide variety
of built-in shapes, objects, and stencils to work with.
Visio can be used to create 3D map diagrams, though the built-in tools for this are limited. It
works well for simple maps that you might print on a brochure or campus directory.
How to use Microsoft Visio:
 Choose and open a template.
 Drag and connect shapes.
 Add text to shapes.

Choose and open a template:

 Start Visio.
 Click the Flowcharts category.
 Click Basic Flowchart, and then click Create.

Each template includes shapes related to the type of drawing, in collections called stencils.
Stencils are in the Shapes window beside the drawing page. For example, one of the stencils
that opens with the Basic Flowchart template is Basic Flowchart Shapes.

Drag and connect shapes:

To create your diagram, drag shapes from the stencil onto the blank page and connect
them to one another. There are several ways to connect shapes, but for now use Auto
Connect. For example, just a few clicks connect a flowchart Start/End shape to a new
Process shape.

1. Drag the Start/End shape from the Basic Flowchart Shapes stencil onto the drawing page, and
then release the mouse button.
2. Hold the pointer over the shape so that the blue Auto Connect arrows show.

3. Move your pointer on top of the blue arrow that points toward where you want to place the
second shape.A mini toolbar appears that contains shapes from the top of the stencil.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

17
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
4. Click the square Process shape.

The Process shape is added to the diagram, automatically connected to the Start/End shape.

Add text to shapes:

1. Click the shape and start typing. You don’t need to double-click to add text to a shape; when
you type, text is added to whichever shape is selected.

2. When you finish typing, click on a blank area of the drawing page or press ESC.

Microsoft Visio component:

Business Graphics:
Visio is an easy-to-use application especially suited for creating business graphics. While
it is best known for creating flowcharts and organizational charts, it can also be used for a
variety of illustration tasks.
Visio Documents
Visio documents are referred to as illustrations, drawings, and diagrams. These terms are
used interchangeably.

Sharper Images
Visio is a vector-based illustration tool. This means drawings are composed of lines that
are computed mathematically which result in sharper images than with bitmapped tools
which are resolution dependent.

Shapes
The basic drawing unit in an illustration is the shape. Shapes can represent both objects in
the real world and objects in concepts. For example, shapes can represent desks on a floor
plan, employees in an organizational chart, or processes in a flowchart. Shapes are grouped
together in Stencils.

Stencils
Stencils hold the basic Master Shapes used for a specific type of drawing. Stencils are
designated by the type of drawing with which they will work best. For example, a flowchart
stencil contains shapes used for flow diagramming.

Drawing Tools

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

18
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
 There are drawing tools available used to create basic graphic objects like lines, circles,
rectangles, arcs, boxes, etc. You can use these tools to create different elements for your
drawings.

Styles
Styles are object attributes used to produce special effects and to add character to your
illustrations. Styles include color, fill patterns, line properties, and features.

Templates
Each new Visio file is based on a template. Templates contain the basic elements needed
to quickly create your illustration. The most important part of the template is the stencil.
The stencil holds the basic Master Shapes used for a specific type of drawing. Templates
are organized by drawing type.

RATIONAL ROSE
Rational Rose is an object-oriented Unified Modeling Language (UML) software
design tool intended for visual modelling and component construction of enterprise-
level software applications. In much the same way a theatrical director blocks out a
play, a software designer uses Rational Rose to visually create (model) the framework
for an application by blocking out classes with actors (stick figures), use case elements
(ovals), objects (rectangles) and messages/relationships (arrows) in a sequence diagram
using drag-and-drop symbols. Rational Rose documents the diagram as it is being
constructed and then generates code in the designer's choice of C++, Visual Basic, Java,
Oracle8, Corba or Data Definition Language.

Two popular features of Rational Rose are its ability to provide iterative development
and round-trip engineering.

Rational Rose allows designers to take advantage of iterative development (sometimes

called evolutionary development) because the new application can be created in stages
with the output of one iteration becoming the input to the next. (This is in contrast to
waterfall development where the whole project is completed from start to finish before
a user gets to try it out.)

Then, as the developer begins to understand how the components interact and makes
modifications in the design, Rational Rose can perform what is called "round-trip
engineering" by going back and updating the rest of the model to ensure
the code remains consistent.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

19
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Rational Rose is extensible, with downloadable add-ins and third-party partner
applications. It supports COM/DCOM (ActiveX), JavaBeans, and Corba component
standards.

Rational Rose is a sophisticated CASE tool with a number of automated features,

including code generation and reverse engineering.

• ROSE = Rational Object Oriented Software Engineering

• Rational Rose is a set of visual modeling tools for development of object oriented
software.
• Rose uses the UML to provide graphical methods for non-programmers wanting
to model business processes as well as programmers modeling application logic.
• Modeling can be useful at any point in the application development process.
• Initial Design Work (Requirement Analysis and Definition)

– Use Cases
– Class Diagrams
– Sequence Diagram

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

20
ENNGINEERING, THE UNIVERSITY OF FAISALABAD
Rational Rose simplifies software development
Rational Rose uses modeling to unify and simplify the software development process.
Rose automatically maintains consistency between the diagram and its specifications.
The following key diagrams are used:

Class diagrams:
Rose uses class diagrams to graphically describe generic descriptions of the system
you’re going to build. Class diagrams contain icons that represent classes and interfaces
and their relationships to one another.

State chart and Activity diagrams:

Rose allows users to use state chart diagrams (which are state-driven) to model the
dynamic behavior of individual classes or objects. State chart diagrams are very similar
to activity diagrams (which are activity-driven).

Interaction diagrams:

Rose uses interaction diagrams as a collective name for collaboration and sequence
diagrams, which, in essence, graphically represent interactions. Collaboration diagrams
show how objects are associated with each other, whereas sequence diagrams show
time-based interactions between objects.

Component diagrams:

Rose uses component diagrams to clearly reflect the physical dependency relationships
between components (i.e., main program, subprogram, packages, and tasks) and their
arrangement in a graphical manner.

Deployment diagrams:

Using the deployment diagram, Rose allows users to graphically show the connections
between processors, devices, and connections.

Task: Write difference between MS Visio and IBM Rational Rose?

1. Control Systems.

LINEAR CONTROL SYSTEMS LAB, SCHOOL OF ELECTRICAL

21
ENNGINEERING, THE UNIVERSITY OF FAISALABAD