Note: This unit version is currently under review and is subject to change!

MTRX1702: Mechatronics 1 (2016 - Semester 2)

Download UoS Outline

Unit: MTRX1702: Mechatronics 1 (6 CP)
Mode: Normal-Day
On Offer: Yes
Level: Junior
Faculty/School: School of Aerospace, Mechanical & Mechatronic Engineering
Unit Coordinator/s: A/Prof Rye, David
Session options: Semester 2
Versions for this Unit:
Site(s) for this Unit:
Campus: Camperdown/Darlington
Pre-Requisites: None.
Prohibitions: ELEC1101 OR ELEC2602 OR COSC1002 OR COSC1902.
Brief Handbook Description: This unit of study aims to provide a foundation for the study of systems and embedded programming for the degree in Mechatronic Engineering.

It is based around a systems engineering approach to requirements capture, software design, implementation, debugging and testing in the context of the C programming language. Problem definition and decomposition; the design process; designing for testing and defensive coding methods; modular code structure and abstract data types; best practice in programming. Programming in teams; documentation and version control.

The C language:

Preprocessor, tokens, storage classes and types; arithmetic, relational and bit manipulation operators; constructs for control flow: if, switch, for, do and while; arrays; pointers and character strings; dynamic memory allocation;functions and parameter passing; derived storage classes: structures and unions; file I/O.
Assumed Knowledge: MTRX1701.
Timetable: MTRX1702 Timetable
Time Commitment:
# Activity Name Hours per Week Sessions per Week Weeks per Semester
1 Lecture 2.00 2 13
2 Tutorial 3.00 1 12
3 Independent Study 5.00 13
T&L Activities: Tutorial: Laboratory-based tutorials.

Independent Study: Students are expected to undertake at least five hours of independent study per week outside of formally timetabled classes. Students are expected to commit to private study, which may include lab work, outside of the time tabled hours. It is expected that the appropriate reference books and web-based material will be read to supplement material presented during 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
Problem definition and analysis, systematic design, implementation and fault-finding in software. Design (Level 2)
Theoretical foundations of software engineering. Engineering/IT Specialisation (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 2)
1. Ability to analyse, design, implement, debug and test programs.
Engineering/IT Specialisation (Level 2)
2. Ability to design and implement complete and correct programs in the C language.
Assessment Methods:
# Name Group Weight Due Week Outcomes
1 Software Engineering Assignment 1 No 25.00 Week 7 1, 2,
2 Software Engineering Assignment 2 No 25.00 Week 12 1, 2,
3 Final Exam No 50.00 Exam Period 1, 2,
Assessment Description: Moderation of Group Work Marks Marks for team-based work may be moderated on the basis of individual effort and understanding as perceived by the lecturer and tutors.

Method of Submission of Written Work Work should ideally be prepared with a word processor and printed for submission. You may hand-write some (e.g. diagrams) or all of your work, but work that is illegible will not be assessed. Please do not write in pencil as it can be very difficult to read under artificial light. A completed copy of the Compliance Statement must be submitted with each assignment to certify that the assignment has been completed in accordance with the University`s policy on Academic Dishonesty & Plagiarism. Work may be submitted on paper or electronically by email. Paper submission: Staple your work and compliance statement inside a manila folder that is clearly labelled with your SID and name, and the subject code MTRX1702. Submit by posting the folder in the box labelled “MTRX1702” that is outside the Purcell Room on level 3 of the Mechanical Engineering Building. Electronic submission: email your work and the signed compliance statement (both in PDF format) to MTRX1702 (at) All assignments are due at midnight on a Friday.

Late Submission of Assignments Late submissions will be penalized 20% of the full mark for every day or part thereof that the assignment is late.

Assignment Extensions and Deadlines No extension of the published due dates and times will be given unless exceptional circumstances apply. In such cases, application for an extension must be submitted in writing (e.g. by email to the component lecturer), citing those circumstances. A decision will be given in writing (email).

Must Pass Both Components To pass this unit of study it is necessary to obtain a mark of not less than 45% in BOTH the Digital Systems and Software Engineering components. If you fail either component the maximum mark you can get for the unit of study is 45%.
Assessment Feedback: Students can expect feedback for this Unit of Study through discussion during lectures and laboratory/project work sessions, and through written responses to questions posed via email. Students can provide feedback to the Lecturer and Tutors by discussion during lectures or tutorial/ laboratory sessions, and by submitting comments and questions by email.
Grade Type Description
Standards Based Assessment Final grades in this unit are awarded at levels of HD for High Distinction, DI (previously D) for Distinction, CR for Credit, PS (previously P) for Pass and FA (previously F) for Fail as defined by University of Sydney Assessment Policy. Details of the Assessment Policy are available on the Policies website at . Standards for grades in individual assessment tasks and the summative method for obtaining a final mark in the unit will be set out in a marking guide supplied by the unit coordinator.
Policies & Procedures: See the policies page of the faculty website at for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.
Recommended Reference/s: Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
  • C: How to Program
  • Digital Design: Principles and Practices
  • The Art of Electronics
  • The C Programming Language
Online Course Content:
Note on Resources: Library classifications: 005.133, 621.3819, 621.39

Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar

Week Description
Week 1 Software Engineering: Introduction
Digital Systems: Introduction
Week 2 Software Engineering: Data types
Digital Systems: Basics of electrical circuits
Week 3 Digital Systems: Basic logic operations
Software Engineering: Arithmetic operations
Week 4 Software Engineering: Decisions and loops
Digital Systems: Boolean algebra
Week 5 Digital Systems: Simplification of logic functions
Software Engineering: Functions
Week 6 Software Engineering: Scope and extent
Digital Systems: Transistors and basic logic families
Week 7 Digital Systems: Practical issues in digital circuits
Software Engineering: Pointers
Assessment Due: Software Engineering Assignment 1
Week 8 Software Engineering: Pointer arithmetic
Digital Systems: Sequential logic
Week 9 Digital Systems: Multiplexers, demultiplexers and other digital integrated circuits
Software Engineering: Arrays and strings
Week 10 Digital Systems: Representation of signed numbers
Software Engineering: Bitwise operations
Week 11 Software Engineering: Dynamic memory
Digital Systems: Design example
Week 12 Digital Systems: Complex design techniques
Software Engineering: The C preprocessor
Assessment Due: Software Engineering Assignment 2
Week 13 Digital Systems: Review and discussion
Software Engineering: User defined types
Exam Period Assessment Due: Final Exam

Course Relations

The following is a list of courses which have added this Unit to their structure.

Course Year(s) Offered
Biomedical - Mechatronics Major 2013, 2014, 2015
Mechatronic 2015, 2016
Mechatronic / Arts 2015, 2016
Mechatronic / Commerce 2015, 2016
Mechatronic / Medical Science 2015, 2016
Mechatronic / Music Studies 2016
Mechatronic / Project Management 2015, 2016
Mechatronic / Science 2015, 2016
Mechatronic / Law 2015, 2016
Mechatronic (Space) 2015
Mechatronic (Space) / Arts 2015
Mechatronic (Space) / Commerce 2015
Mechatronic (Space) / Medical Science 2015
Mechatronic (Space) / Project Management 2015
Mechatronic (Space) / Science 2015
Mechatronic (Space) / Law 2015
Mechatronic (till 2014) 2010, 2011, 2012, 2013, 2014
Mechatronic Engineering / Arts 2011, 2012, 2013, 2014
Mechatronic Engineering / Commerce 2010, 2011, 2012, 2013, 2014
Mechatronic Engineering / Medical Science 2011, 2012, 2013, 2014
Mechatronic Engineering / Project Management 2012, 2013, 2014
Mechatronic Engineering / Science 2011, 2012, 2013, 2014
Mechatronic (Space) (till 2014) 2010, 2011, 2012, 2013, 2014
Mechatronic Engineering (Space) / Arts 2011, 2012, 2013, 2014
Mechatronic Engineering (Space) / Commerce 2010, 2011, 2012, 2013, 2014
Mechatronic Engineering (Space) / Medical Science 2011, 2012, 2013, 2014
Mechatronic Engineering (Space) / Project Management 2012, 2013, 2014
Mechatronic Engineering (Space) / Science 2011, 2012, 2013, 2014
Mechatronic Engineering (Space) / Law 2010, 2011, 2012, 2013, 2014
Biomedical 2016
Flexible First Year (Stream B) / Science 2012

Course Goals

This unit contributes to the achievement of the following course goals:

Attribute Practiced Assessed
Design (Level 2) Yes 37.5%
Engineering/IT Specialisation (Level 2) Yes 37.5%

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.