MECH ENG 3032 - Micro-Controller Programming

North Terrace Campus - Semester 2 - 2015

The focus of this course is on the programming and use of micro-controllers in mechatronics applications. Assuming basic knowledge of the C programming language, the material is presented in a combination of lectures, tutorials and hands-on laboratory sessions. The build process of micro-controller software is examined in detail thereby providing the language for understanding compiler handbooks, on-line publications and micro-controller datasheets. The newly developed skills are then applied in a number of practical case studies covering typical mechatronics applications including servo-mechanisms, sensor interfacing, real-time issues and inter-platform communication. Emphasis will be laid on the confident use of the C programming language using a variety of programming environments. Fault finding techniques will be introduced, ranging from low-level in-circuit debugging to source-level debugging on simulators and evaluation boards. Small-group projects and case studies will be used to provide important hands-on experience with micro-controller based projects.

  • General Course Information
    Course Details
    Course Code MECH ENG 3032
    Course Micro-Controller Programming
    Coordinating Unit School of Mechanical Engineering
    Term Semester 2
    Level Undergraduate
    Location/s North Terrace Campus
    Units 3
    Contact Up to 4 hours per week
    Available for Study Abroad and Exchange Y
    Incompatible MECH ENG 7072
    Assumed Knowledge C programming e.g. MECH ENG 1103
    Restrictions Available to BE(Mechatronic), BE(Mechanical & Automotive) & associated double degree students only
    Course Description The focus of this course is on the programming and use of micro-controllers in mechatronics applications. Assuming basic knowledge of the C programming language, the material is presented in a combination of lectures, tutorials and hands-on laboratory sessions. The build process of micro-controller software is examined in detail thereby providing the language for understanding compiler handbooks, on-line publications and micro-controller datasheets. The newly developed skills are then applied in a number of practical case studies covering typical mechatronics applications including servo-mechanisms, sensor interfacing, real-time issues and inter-platform communication. Emphasis will be laid on the confident use of the C programming language using a variety of programming environments. Fault finding techniques will be introduced, ranging from low-level in-circuit debugging to source-level debugging on simulators and evaluation boards. Small-group projects and case studies will be used to provide important hands-on experience with micro-controller based projects.
    Course Staff

    Course Coordinator: Associate Professor Steven Grainger

    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes
    1 Be able to analyse the needs of mechatronic applications and design appropriate micro-controller based solutions
    2 Have a good understanding of the hardware units within a modern micro-controller
    3 Have a good understanding of the software tools available for the design and testing of micro-controller based applications and the associated software development process
    4 Be able to interface external devices to a micro-controller
    5 Understand the need to undertake lifelong learning
    University Graduate Attributes

    This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

    University Graduate Attribute Course Learning Outcome(s)
    Knowledge and understanding of the content and techniques of a chosen discipline at advanced levels that are internationally recognised. 1,2,3,4
    The ability to locate, analyse, evaluate and synthesise information from a wide variety of sources in a planned and timely manner. 1,2,4
    An ability to apply effective, creative and innovative solutions, both independently and cooperatively, to current and future problems. 1,3
    Skills of a high order in interpersonal understanding, teamwork and communication. 1
    A proficiency in the appropriate use of contemporary technologies. 1,3
    A commitment to continuous learning and the capacity to maintain intellectual curiosity throughout life. 5
  • Learning Resources
    Required Resources

    Lecture Notes provided

    Recommended Resources

    Qing Li, Caroline Yao, Real-Time Concepts for Embedded Systems, CMP Books, New York, 2003, ISBN 1-57820-124-1

    Thomas Bräunl, Embedded Robotics, Mobile Robot Design and Applications with Embedded Systems, Springer, Berlin, 2003, ISBN 3-540-03436-6

    Online Learning
    Jonathan W. Valvano, Developing Embedded Software in C Using ICC11/ICC12/Metrowerks, online book, [last accessed: 10/01/2006]
  • Learning & Teaching Activities
    Learning & Teaching Modes

    The course takes a flexible approach to teaching and learning with material delivered, concepts explored and skills developed using a range of techniques. Interactive lectures are used for presentation of material, exploration of concepts and discussion of directed reading. A series of diagnostic quizzes is used to establish existing knowledge and the assimilation of taught concepts.

    Laboratories are centred upon project based learning with case studies used to provide hands-on experience.

    Workload

    The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

    Indicative workload is 13 hours per week

    Activity Hours
    Lectures 24
    Laboratories 24
    Self study 56
    Directed reading 12
    Assignments 40
    Learning Activities Summary
    Introduction [1 week]
    • Definition of embedded systems
    • Application examples
    • Common micro-controller tasks
    • Typical hardware units within a micro-controller
    • Software development cycle
    • Programming languages for micro-controllers (C, C++, Java)
    • Target Platform: Wytec Dragon12
    • Software IDE: Keil C166, Metrowerks CodeWarrior, GNU gcc

    The build process, fundamentals [1 week]
    • Compiler, assembler, linker
    • Compiler and linker options
    • Keil C166 projects
    • Source level debugging using a micro-controller simulator
    • Debugging using a target monitor
    • Macro definitions, configuration registers and stack frames
    • Memory models and memory maps
    • Memory type specifiers
    • Object classes and storage class

    Micro-controller interfacing [2 weeks]
    • Address, data and control busses
    • Serial, parallel, DMA techniques
    • Interrupts and polling
    • Timing
    • Digital I/O
    • A/D converter
    • Serial communications
    • PWM unit
    • Object classes and storage class

    The build process, advanced concepts [2 weeks]
    • Sections, modules, programs
    • The linker
    • Interpreting the assembler listing
    • Interpreting the linker map file
    • Near data and far data
    • Library files
    • Development utilities
    • Objects file formats: ELF, COFF, DWARF-1/2, S-Records, Intel HEX
    • Optimisation

    Interfacing to Mechatronic Devices [3 weeks]
    • Intelligent instrumentation
    • Transducers
    • Signal processing
    • Motion control
    • Power circuitry

    Embedded control applications [3 weeks]
    • Servo-motor control
    • Stepper motor control
    • Real-time data logger (menu driven, RS-232, communications, adjustable sample rate)
    Specific Course Requirements

    N/A

  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    Assessment Task Task Type Due Weighting Learning Outcome
    Diagnostic quiz Formative

    1

    Assignment 1 Summative 5 15% 1,2,3
    Mid semester quiz Formative 7 1,2,3
    Assignment 2 Summative 11 15% 1,4,5
    End semester quiz Formative 12 1,2,3,4
    Examination Summative 70% 1,2,3,4
    Assessment Related Requirements

    N/A

    Assessment Detail

    Assignment 1 15%
    Requires the design and implementation of software for the sensing and control of mechatronics devices. Submission of an engineering report and developed software.

    Assignment 2 15%
    Requires the design and implementation of interface hardware and software for the sensing and control of mechatronics devices. Student demonstration and submission of hardware and developed software.

    Examination 70%
    3hr open book examination.

    In addition there will be a series of formative quizzes.

    Submission

    Fully commented source code and associated assignment documentation must be submitted through the digital drop box of myUni. Physical reports must be submitted to the Course Submission Box. Late submissions are subject to a penalty of 10% per working day. Re-submissions are not allowed except under extenuating circumstances. Assignments will normally be returned within 2 working weeks.

    Course Grading

    Grades for your performance in this course will be awarded in accordance with the following scheme:

    M10 (Coursework Mark Scheme)
    Grade Mark Description
    FNS   Fail No Submission
    F 1-49 Fail
    P 50-64 Pass
    C 65-74 Credit
    D 75-84 Distinction
    HD 85-100 High Distinction
    CN   Continuing
    NFE   No Formal Examination
    RP   Result Pending

    Further details of the grades/results can be obtained from Examinations.

    Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

    Final results for this course will be made available through Access Adelaide.

  • Student Feedback

    The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

    SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.