Meeting – January 13, 2009 Report Meeting

• Add section about what the project is supposed to do and the components
• Make Work Breakdown Structure more horizon
  • * Add caption about what numbers represent
  • * Can use abbreviations of Names
• On sensors section put headings
• Parallax PING Sensor (say where acquired)
• Sensors figure: Large and Small, explain saturation
  • * Add section about extra waveforms
  • * Leave out section about oscillations
• Arduino
  • * Show the specs and shrink the rest
  • * Put full specs in the appendix
• Motor Controller
  • * Justify purchase
  • * More specifications
  • * Required specs of the H-Bridge IC
  • * Need more specifications in general
• In Scheduling
  • * Refer to first figure
  • * Refer to Gantt Chart
• Division of labour
  • * Investigate new motor and design new motor drive, speced the motor
• Potentiometer
  • * Add to budget
• Move section on specs for microcontroller
• Intelligence Algorithm
  • * Issues with PIR sensors
  • * Different scenarios
  • * Filters
  • * Take information from proposal
• In Gantt Chart
  • * What is meant by construction?
  • * Software integration? Intelligence algorithm?
  • * Put software integration right after component integration
  • * Add caption about completion
  • * Show a second Gantt Chart in Meeting with up-to-date
• Problem and risk management
  • * Risk level → low, medium , high

Aside

• Look into getting a piece of plexiglass that lets infrared

Present:

• Jonathan Mash
• Mike Studli
• Liliane Barbour

Agenda

• Blueprint paper - task assignment

Discussion:

• Liliane is in charge of contacting Dr. Hashtrudi-Zaad to set-up a meeting time
• All team members are to finalize their course schedule in order to plan arranged meeting times
• Task assignments were arranged to optimize the blueprint writting procedure
• Control board and motor control board interfacing standard was discussed and agreed upon

Sensors

• Putting blinders on sensors
  • Problem that it might not detect close objects.
• Need more cure for sensors to each have their own area.
• Need to test thermal sensor → see if can be used to differentiate between objects
• Will order more PIRs later in case some get damaged

Motor

• How much force on gears? Don’t want to break
• If use gears can use a smaller stepper motor
• Algorithm: ramp start and stop
• Spline curve → so can start acceleration with zero slope at beginning and zero slope at end
  • Spline toolbox in MATLAB

Electrical

• Heat sinks
• Do we need an enclosure?
• Test on bigger TVs

Microcontroller

• Need a lot of analog ports → 8?
• Serial output

Ordering plan

• Buy pre-fab controller, and purchase PING, etc.
• When see how much money left, then buy parts for custom controller and PIR sensors
• PERF board
• Need to put PCB boards in the budget

What we need now

• Excel table with minimum costs in a budget
• Possible other budget with custom controller, etc.

For next week

• Budget
• Test thermal sensors
• Test volume
  • Look for evaluation board for controller
  • Ease of programming
  • Power supply
  • memory

Present:

• Dr. Hastrudi-Zaad
• Jonathan Mash
• Mike Studli
• Liliane Barbour

Agenda

• Proposal paper

Discussion:

• Reviewed proposal report

• Looked at web-site

• Clean front end of web-site

• Have some password protection option

Project:

• Check devices but we may need budget approval first
• Contact: Steve Humphrey
• Items and testing devices
• Use volt meter and oscilloscope to test
• Particular bench set-up if we need special equipment
• Research proximity sensors
• Discussed next meeting date
• * field trip next Thursday so the following Thursday November 13th

Deliverables for the next meeting

• Deliverables for November 13th Meeting:
• Look at sensors
• Crude plan of what we want to do
• Present all options (uC, fpga, etc)
• Up-dated budget
• Be ready to start ordering