1 / 10

EE 682L: An Introduction

EE 682L: An Introduction. EE682 Goals Capstone design project Apply engineering practices and techniques Use written and oral communication skills Engage students in teamwork 682L Project: RF Digital Modem Performance: bits/second/dollar Limits: $100 and DL569 lab PCs. Instructors.

joy-short
Download Presentation

EE 682L: An Introduction

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. EE 682L: An Introduction • EE682 Goals • Capstone design project • Apply engineering practices and techniques • Use written and oral communication skills • Engage students in teamwork • 682L Project: RF Digital Modem • Performance: bits/second/dollar • Limits: $100 and DL569 lab PCs

  2. Instructors • Lee Potter, Associate Professor • DL716 • potter.36@osu.edu • Office: MTWF 12:30-1:18 and by appointment • Email daily • Aditi Kothiyal, Graduate Teaching Assistant • DL569 • kothiyaa@ee.eng.ohio-state.edu • Lab hours: MW 4-6; TR 4:30-7:30

  3. Whence 582/682? • Over one-third of engineering time is spent on writing, editing, and preparing reports and oral presentations. • A 1987--1991 survey of OSU Engineering alumni and employers showed preparation mismatched to importance on four topics: • writing skills, oral skills, problem solving, teamwork. • A.B.E.T. encouraged increasing both design experience and teamwork. EE582/682 was introduced in 1995

  4. 682L Course Structure • Project Plan January 22 • Interim Report February 9 • Final Presentation March 8 Jan 22 Design Feb 9 Build Mar 8 Test and Re-design

  5. Course Structure: Finer Scale • Progress report week 2 • Project Plan January 22 • Plan critique week 4 • Interim Report February 9 • Oral presentation week 6 • Progress report week 8 • Oral presentation week 10 • Final Report March 12 • Demo March 15

  6. From Student Feedback… • More team time during regularly schedule hours • 16 team hours • 7 lecture hours • 6 presentation hours • More lab access • 10 hours/week open lab (and by appointment) • Lab shared with EE508 • Review meetings (weeks 2, 4 and 8) • Peer evaluations • Interim report serves as first iteration on the final report • Clarity in schedule, expectations, and evaluation criteria. • Link with EE582

  7. Design Specifications • Build and demonstrate a prototype modem • FCC compliant, 902-928 MHz • Distance 8.25m • Character error rate 0.001 • Data rate 9800 bps • Development cost $100 • Packet duration 7 sec • Delay 30 sec • DL569 PCs • Files and typed text

  8. Design Specifications • Build and demonstrate a prototype modem • FCC compliant, 902-928 MHz • Distance 8.25m (DL569 length) • Character error rate 0.001 (simple to measure) • Data rate 9800 bps (proven reachable) • Development cost $100 (actual budget) • Packet duration 7 sec • Delay 30 sec (processing time) • DL569 PCs • Files and typed text Realistic and realism UHF Wi-Fi; 3 credits, 1 quarter

  9. Resources for Success • Instructors: office hours and lab hours (14 hours/week) • Communications Primer and two lectures • Basics of digital communications • Pointers to further information • Web Links at course web page • Starting points for RF components, antennas, coding, PC I/O, FCC • Free-ware on-line and Matlab toolboxes • Texts on reserve at SEL • EE582 preparation

  10. Hints for Success • Start early • Make good progress before other courses become intense • For reporting, reserve time for editing • Team-work • Identify tasks and partition effort among team members • Take advantage of course resources • Test sub-systems and pay attention to interfaces • In software, leave parameters as variables (for easy mods) • Respect team-mates • Have fun building a working device

More Related