Lab Policy and Grading of Embedded Control Systems
Pre-lab questions
These are questions asked about the concepts that the lab addresses, and often relate to topics covered in the
lecture. Some pre-lab questions also test your knowledge of the MPC5553 and its peripherals. Such questions
can be answered by referring to the relevant sections of the MPC5553 reference manual or to any application
notes that accompany a lab. All of these questions are to be handed in according to the schedule.
Pre-lab code, for use in the lab
Some labs will come accompanied with header files and skeleton library files and instructions about how certain
functions should behave. These functions will be used during the in-lab, and you can, and should, work with
your partners on writing them before beginning the in-lab part.
In-lab experiments
You will work together with your partners on anything in the in-lab section of the lab handout. After everyday
use of the hardware a group member have to sign the hardware log in the plastic binder next to your computer
and note if there were any special occurrences.
Post-lab questions
These are questions about any concepts you have learned about during your in-lab, or inference questions to test
your understanding of what you observed in-lab. You may discuss any concepts for these questions with your
lab partners. You and your partners are required to write up your own solutions separately from one another
for all of the post-lab questions.
Requirements
You must attend 8 lab sessions and hand in all 8 lab assignments (pre-, in- and post-lab) to receive credit for
the course. Pre-labs are due at the start of the in-labs, post-labs are due at 5 p.m., unless otherwise mentioned.
Grading
The semester performance will be graded according to the kind of accomplishment of the tasks, see the criteria
listed below. The evaluation is done for the group of three students. The maximum is 12 points per lab.
Criteria for the rating:
- Correctness and completeness of pre-, in- and post-labs (7 Points)
- Systematic use of documentation (1 Point)
- Ability to debug the code systematically with the use of resources, such as LEDs or the serial port output
(1 Point)
- The way of working, such as team work, independent handling of the exercises, task sharing and integration
of every member in the coding and debugging process (1 Point)
- Handling of the hardware, as taking care, correct usage or overview over the different parts as introduced
during the labs (1 Point)
- Observance of time schedule (1 Point)
- Implementation of additional features not given in lab description (Bonus Point)
1