|
Objective for each group:
- Innovate an embedded system, or
- Research and improve of an existing embedded system
- Make sure that the implementation of the system is completed in 3 weeks
- Each group is responsible for their own components
- May use more than one MSP430 board
- You may borrow any of the components that you have used during the labs
- Keep it “clean” & always practice safety!
- Each group is responsible for the functionality described on the proposal upon check-outs
- Each group needs to checked-out each phase of the final lab with the Instructor
The role of the Instructor & TAs:
- We are not responsible for developing any part of your code(s)
- We will help you in debugging certain parts and advice on the development of code
- Discuss approach to proposed embedded system
- Ask us any questions, especially before writing up your proposal
Phase Zero: Submit a one or two-page proposal
- Describe the embedded system that the group will work on
- Description should be one or two paragraphs
- You may want to attach diagram(s) that show all parts of the system
- This means you need to know in HOW things are connected and/or communicating
- You may use a flowchart to describe functionality of code with hardware
- Make sure that the work can be accomplished in 3 weeks
- Set goals that will help you accomplished a finished lab
- Some of the best goals is to accomplish a working component or two of integration/communications
- Describe the equipment components involved of the system that will be used
- If you are going to order parts, describe from where and expected arrival of your components
- “Parts did not arrive” is not an excused
- Most, if not all, will be implemented on breadboards
- Describe the results you expect to see after each checkout
- What are the results you expect to obtain during the first check-out
- What are the results you expect to obtain during the 2nd check-out
- What are the final results expected in final check-out
- Submit hard copy: Monday 11/18/2013 at the beginning of Lab to TAs & email it to instructor: dvalles@mtech.edu
- If your proposal is inadequate, the group will be ask to either look for a different project, change approach, change parts & rewrite a new proposal before moving on with the final lab. YOU WANT TO AVOID THIS!!!
Phase One:
- Deadline to check-out: 12/2/2013 by 4pm
- Group must be ready to show progress of the lab
- Usually at this point, we expect to see:
- Code that is working towards the final functionality of the system
- Comment code properly
- One or some components working on a “Testing” phase
- Group must demo Phase 1 Goals from the Proposal
- Submit hard copy of initial code to Matt or Clint
Phase Two:
- Deadline to check-out: 12/9/2013 by 4pm
- Group must be ready to show more progress of the lab
- Usually at this point, we expect to see:
- A more complex code that is working towards the final functionality of the system
- Comment code properly
- Components working on a “Beta” phase – they are working but buggy at times
- Group must demo Phase 2 Goals from the Proposal
- Submit hard copy of code at this point to Matt or Clint
Phase Three:
- Deadline to check-out: 12/16/2013 by 4pm
- Usually at this point, we expect to see:
- Full code working and well commented
- The whole system working as mentioned on the Proposal with all the components
|
