electronics design laboratory lecture #12ecee.colorado.edu/ecen2270/lectures/lecture12.pdf · •...

ECEN 2270 1Electronics Design Laboratory

Electronics Design LaboratoryLecture #12

Finishing Lab 5 this week

ECEN 2270 Electronics Design Laboratory 2

• Tuesday: complete Parts A and B• Thursday: Lab 5 demo

Lab 5 demo• The Lab 5 demo should include:

– Complete transmitter circuit, including: data signal generator (can be bench signal generator, or a 555 timer, or another Arduino), modulator circuit (using 555 timer), and the 434MHz transmitter board

– Complete receiver circuit, including: 434MHz receiver board, filter, peak detector, and comparator

– Arduino code used to execute commands based on the data signal received

• As a team: be prepared to demonstrate wireless remote control of more than 1 function (e.g. start/stop, move forward, move back, turn left, turn right) accomplished by changing duty cycle of the data signal on the transmitter side. Upon request, be prepared to show LTspiceschematic of the receiver circuitry and your Arduino code.

• Individually: be prepared to answer questions about circuit design and operation of the transmitter and the receiver.

Electronics Design Laboratory 3ECEN 2830

Project• Must rely on fully functional Lab 2‐4 circuits, optionally Lab 5

– Wireless control is optional: can re‐do Lab 5 wireless, or replace it with a different control method if so desired

– Must include an additional hardware component that requires more than just plugging in a block made by someone else

– Programming only add‐ons or enhancements do not count.

• When selecting components check– Supply voltage requirements– Interface requirements; use data sheets!

• If you need extra parts, order now!– Its always good to have backups of inexpensive parts– Be very careful with parts you don’t have a backup for!


Final project timeline and due items

ECEN 2270 Electronics Design Laboratory 5

• Project Presentation Slides (one ppt or pdf file per group) are due by 5pm on Sunday, Nov 13th via D2L dropbox– At most 3 slides covering your project: group member names, group number.

Explain what you are trying to do and how you are planning to do it. The presentation must include a diagram that shows how the proposed project fits around the robot circuitry.

– Each group will present in class on Monday Nov 14th. The presentation must be rehearsed, and must take no more than 2 minutes. Every group member must participate.

• Milestone 1 check in the lab, Tuesday Nov 15th– Show a system block diagram for your final project (may use diagram from the

presentation)– Detail any extra components you will be needing. Describe their functionality

and any expected issues.– Include a schematic of the additional circuitry that you will be building. Should

have nearly finalized design, start to build and test• Written Project Proposal (up to 5 pages), due from each group by 5pm on

Wed, Nov. 17th.

Project Timeline and Deliverables


• In‐class presentation on Monday, Nov 14: submit ppt or pdf file by 5pm on Sunday, Nov 13

– Up to 3 slides, up to 2 minutes: introduce the project team, explain what you want to do and how you plan to do it. Include a block diagram and/or schematic of the proposed additional components and enhanced functionality

• Written proposal: must upload via D2L by 5pm on Wednesday Nov. 16

– A description of the proposed additional component and enhanced functionality, and an outline of the design and implementation approach, including a block diagram or schematic with part numbers on all additional hardware. The proposal must include a development schedule that shows how the work will be developed and tested in subparts and what portions will be completed by Project Milestones 1 and 2. Include deliverables that you will be able to complete, fallback plans if things don’t work out, and additional components you can add if everything goes better than expected. The written proposal should not exceed five pages.

• Project Milestone 1: Tuesday, Nov 15

– A brief informal update in the lab: show block diagram, schematics, and parts selected for the project.

• Project Milestone 2: Tuesday, Nov 29

– A brief informal update in the lab: describe the progress to date, compare progress to the proposed schedule and explain any changes in scope, schedule and design

• Project demo for grading: Tuesday Dec 6

– One‐page presentation slide due via D2L by 5pm on Monday, Dec 5 : include team member names, group number, and up‐to‐date block diagram or schematic. In the lab, demonstrate to the class the enhanced functionality of the robot, be prepared to answer project related questions

• Project demo in the end‐of‐semester expo: the morning of Thursday, Dec 8

– Show your project to the public

• Final report: due via D2L by 5pm on Friday, Dec 9

– The report should focus on the Lab 6 add‐on project components, and how the components are incorporated with the circuits completed in Labs 1‐5. Provide a full description of the robot additional control circuits with design, simulation, and experimental results. Describe how the project design is split into more manageable sub‐circuits or blocks for design, testing and de‐bugging. Comment on design, hardware and code challenges that you had to work through to get the project circuitry fully operational. Propose future extensions to improve the performance and capabilities.


+

A project example… adding a claw to do: • Object retrieval• Person Chaser• Battle Bot• etc


Need the datasheet!


• 6V power• 7mA Idle• 190mA Running• 1100mA Stall

• Ground• Control input (PWM)

• 700‐2300us pulses• 1500us neutral• 5us dead band width

L7806


+

‐

10VDC 6VDC


Control input (PWM)• 700‐2300us pulses• 1500us neutral• 5us dead band width

electronics design laboratory lecture #12ecee.colorado.edu/ecen2270/lectures/lecture12.pdf · •...

Documents