-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tokgozfurkan
committed
Dec 6, 2021
1 parent
765bd74
commit bb9328e
Showing
3 changed files
with
138 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# EE 463 Homework#3 | ||
|
||
## DC Motor Drive | ||
|
||
### Deadline: 19/12/2020 23:59 | ||
|
||
Please check [evaluation.md](evaluation.md) for other details and evaluation criteria about the project. Open a **private repository**, which you will put all your work into. Please add me (/tokgozfurkan) as a collaborator. | ||
|
||
**1) Motor Drive**<br /> | ||
After graduation, you have started to work Hebelsan AŞ. Your work is to design motor drives for the company. Your boss, who is a very strict and stingy person, wants from you to design a motor drive for a separately excited DC motor with following specifications: | ||
|
||
- Rated speed: 1750 RPM | ||
- Rated voltage: 500 V | ||
- Rated power: 3.7 kW | ||
- Armature resistance: 11.2 Ohm | ||
- Armature inductance: 121.5 mH | ||
- Field resistance: 281.3 Ohm | ||
- Field inductance: 156 H | ||
- Field-armature mutual inductance: 1.976 H | ||
- Field voltage: 300 V | ||
- Inertia: 0.02215 kg.m<sup>2</sup> | ||
- Coulomb friction torque: 0.5161 N.m | ||
- Viscous friction coefficient: 0.002953 N.m.s | ||
|
||
You have a single phase and a three phase voltage sources with 230 V<sub>rms,l-n</sub> at 50 Hz. Also, you have DC voltage source to excite field winding of the DC machine. | ||
|
||
**a)** After checking the warehouse, you found 4 already built devices with appropriate input voltage and current ratings: | ||
- Single-phase half-bridge controlled rectifier, | ||
- Single-phase full-bridge controlled rectifier, | ||
- Three-phase half-bridge controlled rectifier, | ||
- Three-phase full-bridge controlled rectifier. | ||
|
||
|
||
Which of the rectifier circuits is suitable for rated power operation of the DC machine? Explain and show the analytical calculation why other rectifiers are not suitable. | ||
|
||
**b)** Calculate the firing angle for the chosen topology to achieve rated voltage of the DC machine at the output of the rectifier? | ||
|
||
**c)** Simulate the designed circuit on Simulink. Enter the firing angle that you have calculated at part 1.b. Assume that the DC machine works in the rated power conditions. Plot the input voltage and input current of the rectifier on the same graph at steady state. Present the FFT analysis results of the input current. Comment on the results. | ||
|
||
**d)** Plot the output voltage and the output current of the rectifier on the same graph at steady state. Plot the speed and the torque of the DC machine at steady state. Comment on the results. | ||
|
||
**e)** Plot the input current of the armature of the DC motor at transient part. What might be a problem with the resultant current graph? Propose a method to overcome the problem. Explain it in detail. | ||
|
||
**f)** Assume that there is a 10 mH line inductance on each phases. Calculate the required firing angle to maintain the rated voltage of the DC machine. | ||
|
||
**g)** Show that the output voltage is remained unchanged. Repeat the part c. Comment on the results. | ||
|
||
**h)** Propose a method to drive the DC machine in reverse direction as well. Explain it in detail. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Homework 3 Team Members | ||
|
||
Random generated teams are announced below. It is your responsibility to find your team member. | ||
If you can not contact your team member, please let me know as soon as possible. | ||
|
||
| Team No | First Member | Second Member | | ||
|--------- |-------------- |----------------- | | ||
| 1 | ecem karamercan |kubilay kaya | ||
| 2 | ugur cem erdem |kaan tutek | ||
| 3 | zehra gunes |alper soysal | ||
| 4 | anil yalcinkaya |ozgur arda kucukaslan | ||
| 5 | mert eren kandilli |ertugrul yolcu | ||
| 6 | musa ulusoy |muhammet samet yakut | ||
| 7 | osman yucel |goktug tonay | ||
| 8 | berna corak |zeynep coklu | ||
| 9 | husnu oguz yorgancilar |emre cakmakyurdu | ||
| 10 | emre celen |tugce sevval kaya | ||
| 11 | ece irem yazir| | ||
|
||
|
||
If your name is not listed above, please let me know. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
|
||
|
||
## Guideline for Homework #3 | ||
|
||
Here are the important points for Homework #3 | ||
|
||
- You will complete the project in pairs. | ||
- You are required to create one Github repo in one of the team member's account. Then please add Furkan (/tokgozfurkan) as collaborator. Each partner is required to contribute to the work. | ||
- You can use any simulation software you want, but it is advised to use MATLAB Simulink. | ||
- At the end of the homework, you are required to submit a project report (in PDF) to ODTUClass. Both this report and your source files in the GitHub repo will be used for grading. | ||
- Reports will be checked using Turnitin, and copying will not be tolerated. Even if you find a report, so that you can inspire, you are limiting of what you can learn from this course. Don't fool yourself, and do your projects with your team member only. | ||
- Late submissions will be available in 1 days after the deadline but the homework will be graded over 85 pts. (-15% reduction for late submissions) | ||
|
||
## Evaluation | ||
|
||
The project will be evaluated using the following guideline: | ||
|
||
**Number of Commits (10%):** The number of edits of your project files as seen from the contributors list. For example, if you start making your project in the last few days, you’ll get no credit. If you start early and continue editing your files, you’ll get full credit. The projects are time consuming, so this is a way to encourage you to start early and work regularly. Note that, each student will be evaluated separately according to personal commit number. | ||
|
||
**Report Quality (Pass or Rejection):** Text explaining your design decisions, quality of your figures, citing relevant studies and your conclusion section. | ||
|
||
**Technical Level (90%):** The detail level of your simulations and your conclusions. | ||
|
||
## Number of Commits: | ||
|
||
In this project the minimum expected number of commits on different days is 2. Each days you made at least one commit is 5 points (saturating at 10 points). The following rules apply: | ||
|
||
- Each student will be evaluated personally. So please make sure each team member contributes. | ||
|
||
- Your commit has to be a meaningful, and considerable amount of change has to be made compared to the previous version. For example, just changing a few words in your report is not a meaningful commit. | ||
|
||
- Number of days that you committed will be evaluated by common sense. For example, a commit at 23:58 and another commit at 00:02 will still count as one. | ||
|
||
- Do not try to find a workaround. Just spend time on your project, and improve your models regularly and it should be fine. | ||
|
||
You'll get 5 points from the content of your commit messages. You are supposed to write clear and explanatory commit messages, listing what specific improvements that you made in that version. Please have a look at the following links: | ||
|
||
- [Writing Good Commit Messages](https://vip.wordpress.com/documentation/commit-messages/) | ||
|
||
![](https://imgs.xkcd.com/comics/git_commit.png) | ||
|
||
## Report Quality: | ||
|
||
You report quality will be evaluated using the following criteria: | ||
|
||
- The report has an introduction section that briefly explains the content and the aims of the report | ||
- The report organized properly with clear sections and subsections | ||
- All figures and tables have proper captions | ||
- Figures are given with white background | ||
- The graphs have proper axes labels and font size of labels is adequate | ||
- No grammar/spelling errors and very well-written report (hint: use spell-check, Grammarly | ||
- Use *Export Figure* command of MATLAB instead of screenshot | ||
- No equations or any comments presented as a photo of written copy | ||
|
||
If the report is not qualified well enough, the report will be rejected and students will be asked to resubmit the report in three days. The second submissions or late submissions will be evaluated over 85 pts. | ||
|
||
## Technical Level: | ||
|
||
Following grades will be applied for the technical parts: | ||
|
||
- Q1: 100 pts | ||
- a) 10 pts | ||
- b) 10 pts | ||
- c) 20 pts | ||
- d) 10 pts | ||
- e) 15 pts | ||
- f) 10 pts | ||
- g) 10 pts | ||
- h) 15 pts |