Speed Regulation and Control

for a DC Motor

Final project report for the class of Electrical Machines

Submitted to

Dr. Mohammad Salah

Department of Mechatronics Engineering

The Hashemite University

By

Student 1 Name (Student Number)

Student 2 Name (Student Number)

Student 3 Name (Student Number)

Student 4 Name (Student Number)

Student 5 Name (Student Number)

Second Semester 2008/2009

ABSTRACT

This is a short section, usually one or two paragraphs, which summarizes the report. It should summarize your entire work presented without getting into specific details. Major findings and/or contributions should be brought up without the lengthy details of how that was achieved. It should not be more than one page in length.

Hint: It much easier to write the abstract before you complete the report.

ii

TABLE OF CONTENTS

ABSTRACT ii

TABLE OF CONTENTS iii

LIST OF FIGURES v

LIST OF TABLES vi

SECTION 1: Introduction 1

1.1  Problem Statement 1

1.2  Scope and Objectives 1

1.3  Motivations and Importance 1

1.4  Methodology and Implementation 1

1.5  Document Overview 1

1.6  Second Level Heading 1

1.6.1  Third Level Heading 1

SECTION 2: System Description and Design 1

2.1  System Description and Components 1

2.2  System Design 1

2.3  Block Diagrams and Flowcharts 1

2.4  Drive Circuit 1

2.5  Calculations and Parts Selection 1

2.6  Final Design 1

SECTION 3: Discussion 1

3.1  Test Procedure and Load Application 1

3.2  Discussion 1

3.3  System Advantages and Disadvantages 1

SECTION 4: Conclusions and Future Work 1

4.1  Conclusions 1

4.2  Future Work 1

REFERENCES 1

Appendix A: Parts Data Sheets 1

A.1  First Element 1

A.2  Second Element 1

Appendix B: Program Listings 1

B.1  First Program 1

B.2  Second Program 1

LIST OF FIGURES

Figure 1.1: System block diagram 1

LIST OF TABLES

Table 1.1: System parameters 1

ii

SECTION 1: Introduction

Each section should begin with an introduction that tells what you will cover in the section. It should tell the reader what is in the section as well as its importance to the overall report. This introduction should occur directly below the section heading and does not require its own header.

The introduction briefly describes the existing literature (literature review) about your project, research, or problem that needs to be solved. The introduction also states the objectives of your work or the work that has been performed so far. The contents of your report should be introduced in general.

1.1 Problem statement

In your report, this is the introduction to your work where you describe the overall problem you are trying solve. This section should not assume that the reader has any knowledge of the specific area in which you are working or the specific tools, techniques, and methods you plan to use. You must explain everything to them.

Figure 1.1 is an example of how to insert figures and use captioning. The figure itself should be centered and fall within the margins of the report. You should use the report figure style for each figure and/or table. The caption should follow the figure and table immediately. Follow the format provided in this template to insert figure and table captions. Do not use a period at the end of the caption.

Figure 1.1: System block diagram (figure example)

1.2 Scope and Objectives

In this subsection, you should define what you will and will not attempt to do in this project. Objectives are usually fairly broad – not more than 3 or 4 – and you should include specific requirements later in the report.

1.3 Motivations and Importance

Here you want to state what your motivations to choose this project are…..Also, you want to discuss the importance of the project.

1.4 Methodology and Implementation

In this subsection, you should explain your approach to solving the research problem. You should not only tell the reader “what” you will do, but “why” as well. If you simply state what you did, you may leave the reader wondering why you did what you did. Furthermore, you should explain briefly how you have implemented it.

1.5 Document Overview

Here you are to give your reader a guided tour of the remainder of the document. It should be more than just a list of the upcoming sections. You should effectively overview the background, methods, and results of your report in two or three paragraphs.

1.6 Second Level Heading

Each section will usually be broken down into major subsections. Each subsection should have its own header as shown here.

1.6.1 Third Level Heading

Each major subsection may also be broken down into sub-subsections. Each sub-subsection should also have its own header as shown here.

SECTION 2: System Description and Design

Each section should begin with an introduction that tells what you will cover in the section. It should tell the reader what is in the section as well as its importance to the overall report. This introduction should occur directly below the section heading and does not require its own header.

This is the right place to present the precise description of the system components and state your objectives. In addition, a presentation for the system design is required with all the appropriate design steps.

2.1 System Description and Components

2.2 System Design

2.3 Block Diagrams and Flowcharts

2.4 Drive Circuit

2.5 Calculations and Parts Selection

2.6 Final Design

SECTION 3: Discussions

Each section should begin with an introduction that tells what you will cover in the section. It should tell the reader what is in the section as well as its importance to the overall report. This introduction should occur directly below the section heading and does not require its own header.

This section discusses the end results obtained from the proposed system after the project is implemented and tested. It also discusses the advantages and/or disadvantages of the proposed design and methods in which the system performance can be improved or modified.

3.1 Test Procedure and Load Application

3.2 Discussion

3.3 System Advantages and Disadvantages

SECTION 4: Conclusions and Future Work

Each section should begin with an introduction that tells what you will cover in the section. It should tell the reader what is in the section as well as its importance to the overall report. This introduction should occur directly below the section heading and does not require its own header.

This section concludes the work done in the project and how the proposed system design is justified. This section is the place where you sum up your work. Ways to improve the system is also presented. This is your final chance to convince the reader that your work is important project. You can begin by over viewing what you have just presented to the reader, making sure to point out the important parts one more time. In addition, future work that may enhance the scope of the project should be included.

4.1 Conclusions

However, this subsection should go well beyond simply a recap of your report work. It should tell the reader why what you did is important. Take your results and convince the reader that what you did advances the state of the art and beyond that, is a stepping stone to even greater things.

4.2 Future Work

In this subsection, you should describe the research that could be follow-on work based on your work. It might be things you did not have a chance to complete, or research that your efforts have enabled. As you are the expert now, you should provide as much detail about how this research should be accomplished and what type of methods, techniques, and tools would be the best choices.

REFERENCES

You are requested to use the IEEE citation style. Any citation style is set up to give the reader immediate information about sources cited in the text. In IEEE citations, the references should be numbered and appear in the order they appear in the text. When referring to a reference in the text of the document, put the number of the reference in square brackets. Eg: [1]. For more assistance in using the IEEE citation style, download the pdf file called “IEEE Citation Style Guide”.

Appendix A: Parts Data Sheets

The appendices are used for what should not be included in the main text. If the material presented in your report is secondary or consists of long details, not critical to understanding the basic project, it should be in an appendix. There might be a number of things you want to put into an appendix such as electrical circuit diagrams, user manuals, test results or experimental results. Typically, you want the body of your report to flow smoothly with more detailed information in the appendices.

A.1 First Element

A.2 Second Element

Appendix B: Program Listings

The appendices are used for what should not be included in the main text. If the material presented in your report is secondary or consists of long details, not critical to understanding the basic project, it should be in an appendix. There might be a number of things you want to put into an appendix such as electrical circuit diagrams, user manuals, test results or experimental results. Typically, you want the body of your report to flow smoothly with more detailed information in the appendices.

B.1 First Program

B.2 Second Program

ii