Microcontroller Programming Laboratory#
Our colleague Dr Timothy Davies designed the Microcontroller Programming laboratory to teach you the fundamentals of programming microcontrollers.
Associated with this Laboratory is a Getting Started Guide, and five microcontroller experiments designed to give you the experience of programming a microprocessor (in this case an Arduino Nano based on the Atmel ATMega32 microcontroller) in the C-language and interfacing it to digital and analogue signals. We expect you to record the results of your experiments using a Lab Diary which will be submitted in at the end of the laboratory for assessment.
Lab Experiments#
The Microcontroller Laboratory consists of a getting started introduction, plus the five assessable experiments listed below.
Assessment of the Microcontroller Laboratory#
The mark for each of the experiments is a maximum of five points, making a total of 25 marks – 25% of the assessment for the whole module.
Assessment will be based on a Laboratory (Lab) Diary. Many other lab-based modules are assessed this way, including EG-152 Electronic Circuits next term, and the two practical labs in second year, EGA222 and EGA223.
About the Lab Diary#
What is a laboratory diary?
In the “old days” this would have taken the form of a hard-backed notebook, called a logbook, and all results, calculations and other details of the experiments would be meticulously written in the logbook. This is the 21st Century, and we now use an electronic logbook which we call a Lab Diary.
The lab diary takes the form of a Word document or similar, in which all the details of an experiment are recorded. This might include tables of results, graphs or calculations based on the results, screen shots from the Lab PC or the R&S oscilloscope, photos of the equipment, anything that helps someone reading the diary (including your yourself) to see what was done. In addition, if you are asked to write a report on a particular subject (for example, in EG-152, EGA222 and EGA223) then the lab diary is the source of information for each experiment. You should not need to go back to the laboratory to repeat parts of the experiment. More information about lab diaries, including an example and template is given on Canvas on the page ✅ To Do: Obtain and Keep a Lab Diary 📓.
The script for each of the experiments will tell you what is required for each experiment. In general, this will be programme listings (properly formatted and with copious comments, of course!) and some measurements and calculations based on the results. The lab diary will be submitted later in the term for assessment. It recommended that you convert the submitted version of the diary to pdf, so that we see your document without changes caused by printer drivers, different versions of WORD, and so on.
Questions and Discussion#
If you have questions about any aspect of the Microcontroller Programming Laboratory, please visit the discussion board on Canvas:💬 ❓ 🧪 Discussion and Questions about the Microcontroller Programming Lab Exercises. See also 💬 ❓ 📓 Discussion and Questions about Lab Diaries.
Good luck!#
Good luck with the EG-151 microcontroller programming experiments!
- Dr. Chris Jobling, Module Coordinator
- Dr. Timothy Davies, Creator of the Lab
- Dr. Ben Clifford, Former Module Lecturer