ELEC5303: Computer Control System Design (2013 - Semester 1)
| Unit: | ELEC5303: Computer Control System Design (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Postgraduate |
| Faculty/School: | School of Electrical and Information Engineering |
| Unit Coordinator/s: |
Dr Shrivastava, Yash
|
| Session options: | Semester 1 |
| Versions for this Unit: | |
| Site(s) for this Unit: |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | None. |
| Brief Handbook Description: | This unit aims to teach the basic issues involved in the analysis and design of computer-controlled systems. The emphasis is on theory rather than technological application or industrial practice. However, students are expected to test some of these ideas on a few benchmark control problems in the laboratory. Completion of the unit will facilitate progression to advanced study in the area and to work in industrial control. This unit assumes a basic knowledge of calculus, functions of real variables, Laplace transform, matrix theory and control theory. The following topics are covered. Sampled data systems: aliasing. Zero order hold equivalent: inverse of sampling, sampling system with time delay. Properties of difference equations: solution, stability, change of co-ordinates, Z transform. Input output models: pulse response, pulse transfer operator, pulse transfer function, interpretation of poles and zeros. Analysis of discrete time system: stability (Jury's test, Nyquist criterion, Lyapunov method), sensitivity and robustness, observability (observers, reduced order observers), reachability and controllers, loss of reachability/observability through sampling, output feedback, the Separation theorem. Optimal control: Kalman filter, linear quadratic regulator, output feedback, the Separation theorem. Approximating continuous time controllers. Finite word length mplementations. |
| Assumed Knowledge: | This unit assumes a basic knowledge of calculus, functions of real variables, Laplace transform, matrix theory and control theory. |
| Lecturer/s: |
Dr Shrivastava, Yash
|
||||||||||||||||||||
| Timetable: | ELEC5303 Timetable | ||||||||||||||||||||
| Time Commitment: |
|
||||||||||||||||||||
| T&L Activities: | Tutorial: Problem solving sessions. They also use computing facilities at times. Independent Study: Students need to do some preparation for tutorials. They may also need to read the text and other references to fully master the basic concepts covered in the lectures. |
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
| Attribute Development Method | Attribute Developed |
| Proficiency in creatively applying technical principles, design methodology, and knowledge of tools and materials in the design of computer control systems. | Design (Level 4) |
| Develop in-depth technical skills and knowledge of computer control systems. | Engineering/IT Specialisation (Level 5) |
| Knowledge in how to produce clear and well-constructed engineering documents and informative diagrams and models for computer control systems. | Communication (Level 2) |
| Develop an understanding of the theory behind computer controlled systems and the technological applications of computer-controlled system in parcatice. | Professional Conduct (Level 2) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.
Design (Level 4)| Assessment Methods: |
|
||||||||||||||||||||||||
| Assessment Description: |
Tutorials: There will be 11 tutorials (of duration 2 hours each) during the semester. Tutorials will include analytical problem solving sessions on the material covered in the lectures and computer aided solution / illustration. These sessions will give you the opportunity to explore the concepts in detail and are very helpful in understanding the material covered in the lecture. They will also require you to model and simulate dynamic systems and controllers in Matlab. Tutorials 2-11 are worth 2 marks each and you will be awarded a mark of 0, 1, or 2 based on your participation and completed work during the tutorial. Besides this incentive, in my experience I have found that there is a direct correlation between the tutorial participation and the exam performance of the students. The solutions for the tutorials and computer codes will be available from the unit of study web page after the session. Midterm Exam: The midterm exam is scheduled to provide you an assessment halfway through the semester and more importantly to give you a practice run for the final exam. It will be of the same format as the final exam (but of shorter duration). Again the solutions will be available on the unit of study web page after the exam. Both the midterm exam and the final exam will be based on the lecture material and tutorials. Both exams will be closed book and closed notes. They will test your conceptual understanding of the material. Any complex formulae needed, will be provided on the question paper. Final Exam: Final Exam |
||||||||||||||||||||||||
| Assessment Feedback: | Marked Mid-Sem Exam will be returned to the students. There is detailed discussion during tutorials. | ||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||
| Faculty Policies & Procedures: | Academic Honesty in Coursework. All students must submit a cover sheet for all assessment work that declares that the work is original and not plagiarised from the work of others. Coursework assessment and examination policy. The faculty policy is to use standards based assessment for units where grades are returned and criteria based assessment for Pass/Fail only units. Norm referenced assessment will only be used in exceptional circumstances and its use will need to be justified to the Undergraduate Studies Committee. Special consideration for illness or misadventure may be considered when an assessment component is severely affected. This policy gives the details of the information that is required to be submitted along with the appropriate procedures and forms. Special Arrangements for Examination and Assessment. In exceptional circumstances alternate arrangements for exams or assessment can be made. However concessions for outside work arrangements, holidays and travel, sporting and entertainment events will not normally be given. Student Appeals against Academic Decisions. Students have the right to appeal any academic decision made by a school or the faculty. The appeal must follow the appropriate procedure so that a fair hearing is obtained. Note that policies regarding assessment submission, penalties and assessment feedback depend upon the individual unit of study. Details of these policies, where applicable, will be found above with other assessment details in this unit outline. All university policies can be found at http://sydney.edu.au/policy Various request forms for the Faculty of Engineering and IT can be found at http://sydney.edu.au/engineering/forms/ |
| Prescribed Text/s: |
Note: Students are expected to have a personal copy of all books listed.
|
| Online Course Content: | Learning Management System (LMS) through MyUni |
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
| Week | Description |
| Week 1 | Introduction to Computer Controlled Systems |
| Week 2 | ZOH equivalent, sampling systems with time delay, inverse of sampling |
| Week 3 | Properties of discrete-time systems |
| Week 4 | z-transform, Pulse-transfer function, Interpretation of poles and zeros, Selection of sampling rate |
| Week 5 | Stability analysis of discrete-time systems, Jury’s test, Lyapunov’s method |
| Week 6 | Frequency response function, Bode plots, Nyquist plot and Nyquist criterion, Sensitivity and robustness |
| Week 7 | Controllability, Reachability, Observability, Detectability, Kalman’s decomposition, Loss of reachability and observability through sampling |
| Week 8 | Mid-Sem Exam |
| Assessment Due: Midterm Exam | |
| Week 9 | Pole-placement Controller Design, Regulation by State feedback, Integral Action, Deadbeat Control |
| Week 10 | Pole-placement Observer Design, Deadbeat observer, Current time and reduced order observer, Output Feedback |
| Week 11 | Kalman Filter: motivation and formulation |
| Week 12 | Linear Quadratic Regulator (LQR): motivation and formulation, Optimal Output feedback controller in the presence of random process noise and measurement noise |
| Week 13 | Approximating continuous-time controllers, Finite word length implementation |
| Exam Period | Assessment Due: Final Exam |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| Project Management and Teamwork (Level 2) | No | 0% |
| Design (Level 4) | Yes | 30.66% |
| Engineering/IT Specialisation (Level 5) | Yes | 61.33% |
| Maths/Science Methods and Tools (Level 3) | No | 0% |
| Information Seeking (Level 2) | No | 0% |
| Communication (Level 2) | Yes | 4% |
| Professional Conduct (Level 2) | Yes | 4% |
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.