1 / 31

Design Through Curriculum on Embedded Systems

Design Through Curriculum on Embedded Systems. Team: Aisha Grieme, Jeff Melvin, Dane Seaberg Advisors: Dr. Tyagi and Jason Boyd Client: Dept. of Electrical and Computer Engineering. Problem Statement Concept Diagram and Sketch Requirements Deliverables. Requirements. Problem Statement.

alfreda-mayer
Download Presentation

Design Through Curriculum on Embedded Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Through Curriculum on Embedded Systems Team: Aisha Grieme, Jeff Melvin, Dane Seaberg Advisors: Dr. Tyagi and Jason Boyd Client: Dept. of Electrical and Computer Engineering

  2. Problem Statement Concept Diagram and Sketch Requirements Deliverables Requirements

  3. Problem Statement Students end each year with a wealth of new knowledge without having had the opportunity to use concepts from multiple courses in a single project

  4. Concept Description • Design a system for use in a design course to link curriculum concepts from junior Computer Engineering courses • Multiple tracks in Computer Engineering program • Focus to be applied on embedded systems • Topics will be enforced through a team embedded systems project • System will require teams to apply curriculum concepts from courses

  5. Concept Diagram

  6. Conceptual Sketch

  7. Operating Environment Embedded system laboratory

  8. User Interface Description • AVR Studio 4 & JTAG • Push Buttons • LCD • Terminal • Microsoft Windows

  9. Functional Requirements • One-half semester • Must have clear documentation • Must focus on an adequate sample of curriculum course concepts

  10. Nonfunctional Requirements • Platform must be easy to use • Must be adaptable for new curriculum or curriculum concepts

  11. Market Survey • Performed by Sophomore Design Through Curriculum on Embedded Systems • Students showed preference for a “build your own robot” embedded systems project

  12. Deliverables • Course outline • Demonstrable design project • System documentation

  13. Work distribution Recourses and Costs Schedule Risks Project Plan

  14. Resource and Cost Estimate Time Resource Course Resources • The department has all the hardware, and the software is open source • JTAG Programmer - $300 • iRobot Create - $130 • Cerebot II - $40 • Peripheral Hardware

  15. Risks and Mitigation Plan Time • Risk: The student may not be able to complete the project within the allotted time • Mitigation: Create a timeline for the students to follow and have checkpoints for the students to meet Lack of Background • Risk: Students may lack the background to be able to follow the curriculum • Mitigation: Define a specific skill set and course background to take the class.

  16. Course Plan Course Hardware Considerations Design Details

  17. Course Plan • Week 1: • Get robot, software, and project requirements • Develop process model and project schedule • Week 2: • Learn about the system and begin programming • Set up subversion for the team • Week 3: • OS should be loaded • Robots should be communicating • Develop algorithms in embedded systems

  18. Course Plan • Week 4: • Algorithm design should be finished • Learn about timing in embedded systems • Week 5: • Finish algorithm implementation • Week 6: • Testing will begin • Week 7: • Student will demo their robots

  19. Hardware Considerations * Access to this functionality was not available, but may have been granted upon request

  20. NI cRIO • Used by previous project • OS functionality not available • Possibility of getting some functionality • Interfaces with labVIEW

  21. Vex PIC V0.5 • Interfaces with RobotC IDE • Documentation shows support for needed functionality • Proprietary • Non-Vex add-ons

  22. Bug Labs BUGbase • Runs Linux, has full support of needed functionality • Interfaces with Eclipse • Limited emulator functionality • Recently Released

  23. Arduino Mega • Plenty of memory • Available OS has limited functionality • IDE for board primitive • No components • Which will work • Drivers

  24. Cerebot II and iRobot Create • Familiarity • Board • IDE • OS choices limited • Femto OS • Drivers for components written

  25. Course Demo Testing Lessons Learned Conclusion Implementation

  26. Build and Demo • Synchronized “dancing” and playing music • Shell interface • Bluetooth communication with computer

  27. Testing • System Tests • Femto OS API • Open Interface • Dual Robot Communication • Course Testing • Lab with target student demographic • Survey and questionnaire

  28. Lessons Learned • Need to define research requirements well • Importance of adhering to decisions • Consequences of an incomplete design • Value of seeking expertise in areas of unfamiliarity

  29. Future Work • Research and test a more feature rich OS • May require additional hardware research • Student and TA instructions • Course Testing

  30. Questions?

More Related