mechatronics project
Project description
Title Page
Table of contents
Introduction
? What did you build
• Brief description with photo (100).
• Brief outline of the work you carried out (200).
? Outline of the topics covered in this write-up (200)
Theory of operation
? Functional Block diagram
• Draw the functional block diagram
• Explain each block (200 each)
Component description and identification
• Each component type should be described
• How the components are identified with regard to value and polarity (100 each with photos and circuit symbols)
For each component type you will have received particular instructions covering how it should be mounted and the rationale for same. This dialogue should cover the procedures that you followed in relation to the soldering of such components as the header pins and many others.
Build log and debug
? Problem list
The depth of your learning will be reflected in the extent to which you have identified problems and mistakes that you have made and your description of how you remedied each issue. Investing time and effort in this part of the write-up will yield good results.
System test
? Visual Checklist
• Swap your finished board with a colleague. Conduct a detailed visual inspection noting all items of non-compliance such as:
Correct component values
Component orientation
Solder bridges
Quality of solder joints
• Write-up the results of this inspection and give it to your colleague
• Write a response to each item raised in relation to your board i.e. component changed, resoldered or a justification why you have chosen not to remedy the issue
? Test Schedule
• Record the results of the test schedule and paste the Test Schedule document into this write-up
Programming
• Describe the programming environment
•
Daughter Board
• Layout plan
• Function of board
•
Applications and future developments (400)
You have constructed and programmed a multi-purpose microcontroller board. Outline an application that you wish to use this board for. Your commentary should contain technical detail with regard to the hardware and software requirements. While the detail should be realistic you are allowed to suggest both hardware and software requirements that you may not have yet covered in your course and may not know how to implement.
Project reflection
This is where you can offer your opinion with regard to the value of the learning that you have experienced. You must be critical and forthright, expressing your views clearly and directly. How could the project learning experience be improved? Did you get sufficient support? (be honest!). This information will be used in a process of continuous course improvement.
Bibliography