Started at 1:01pm Presentation notes: Started without connecting to the audience Should directly interact, not just attempt to “emotionally resonate” as a connection. Should have explained the product clearly before jumping into details We may have started explaining specifications or technical detail before giving a general overview of the product clearly References should come after conclusion Catherine notes: Do user trials with a basic prototype device early, before everything else Dr. Young Notes: Be specific about completely blind rather than visually impaired Jonathan Notes: Consider adding audible alerts in addition to haptic feedback. Website notes: Nothing should be changed on the senior design proposal section of the webpage. Ensure that any connected drive documentation is copied as to not affect proposal documentation. Keep working on timeline as we go Combine any indexes with identical start and end dates Update webpage to show empty timeline (to be filled in) Create a modified timeline to show updated proposed timeline (don’t change the one in proposal tab). ·Update all webpages for senior design to contain pertinent information Project notes: Updated rubrics are available on the canvas webpage This includes new design implementation rubric, which pertains to actual design and conduct of the design semester project Report notes: New chapter for report, chapter 3, contributions of project description There are many other changes to report, see rubric for more information Meeting adjourned at 1:31pm

Started at 1:04pm Presentation notes: Website notes: Need to figure out some way to have a different blog or something for the progress log Don’t make it a separate menu element Timeline needs to be updated to show internal user trials in addition to external (internal should be early Time and effort fix, 14 hour prototyping should be the first index Project notes: Add IR sensors to the prototype device to more closely align with the end product Move forward adding audible feedback Deliverables: Updated prototype testing Meeting adjourned at 1:34pm

- No Meeting -

Started at 12:31pm Presentation notes: Website notes: Combining items on the linear timeline and making in order Project Notes: Just do circuit diagrams in Multisim/Pspice Make sure there is no cross talk between the sensors Will be a good idea to start to talk to Francisco and Dylan regarding learning KiCad for PCB design Make sure to document troubleshooting so we can include in chapter 3 in the report. Also will be important to discuss during the presentation. Deliverables: Pulse width modulation to affect speed of the motors (Anthony) Working on simulation and circuit schematics (Lazaro) Working on collector design for face connection (Lazaro) Fixing the timeline and other general website maintenance Meeting Adjourned at 1:12pm

Started at 1:04pm Presentation notes: Website Changes Weekly timelines are purposed toward completing a single objective per week, helps keep students on track Don’t change budget, we will have to things: expenses and cost (expenses are everything we spend such as repeat items, and cost is the cost of the materials used in the final product.) Deliverables: Fix weekly timeline Change monetary budget to monetary expenses Meeting Adjourned at 1:46pm

- No Meeting -

Started at 1:00pm Presentation notes: Website Changes Weekly timelines are purposed toward completing a single objective per week, helps keep students on track Don’t change budget, we will have to things: expenses and cost (expenses are everything we spend such as repeat items, and cost is the cost of the materials used in the final product.) Budget Should be expenses (actual money spent on repeat parts and such) and budget (cost of components in final product). Deliverables: Fix weekly timeline Change monetary budget to monetary expenses Work on system according to what components arrive in time Meeting Adjourned at 1:45pm

Started at 1:00pm Informed Dr. Ejaz regarding week of 27th where I will be out of town Linear timeline needs to be exclusively weekly goals (short term goals for each week, there should be no entry more than a week, if something takes longer, enter the same as a repeated entry for the next week). Change cost of project to Expeneses (Website) Weekly Meetings should go by meeting number not week number, fix formatting, add dates (Website) Deliverables: Fix linear (weekly) timeline Put together all IR sensors with ADC multiplexer Fix weekly entries Meeting Adjourned at 1:46pm

Started at 1:01pm · Do not forget to fix the linear timeline. It is supposed to · Fixing some structural stuff · First week of November we should be doing final testing Deliverables: · Put as many motors together with as many sensors as we have on breadboard (Ant) · Fixing Timeline Stuff (Laz) · Fixing up CAD design (mounting, gaps, etc..)) (Laz) Meeting Adjourned at 1:37pm

Started at 1:02pm · Linear timeline almost fixed, but needs to be meeting to meeting instead of Sunday to Sunday Deliverables: · Finish printing so we can start soldering (Lazaro) · Not meeting next week, taking two weeks to finalize the rest of the final product and begin testing by first week of November 5th. Meeting Adjourned at 1:32pm

Meeting 11:

Started at 1:01pm Deliverables: · Testing the finished product by next meeting so we can submit report by the 28th · If we can start doing something for the report that would be great. Meeting Adjourned at 1:21pm

Meeting 13: Meeting start: 1:02pm Meeting adjourned: 1:51pm We will be meeting on Tuesday the 25th at 10:00am as our last meeting before the report is due. That day we will be reviewing what should be the final report. Just finishing touches or checking things that need to be reviewed. Chapter 3 will be the biggest new contribution. For chapter 2 (background research) is about things that existed previously (software that we used, components we used, etc...). Contributions toward the project are irrespective of who did the work, it is just the work or responsibilities that went into creating the project. (i.e. building the frame, programming the sensors, wiring the internals). Don't have to write the names of the people who did the work. Have substantial number of chapters done for next week to review. Need to test each requirement specifically. Another link will be needed, final testing and results, in the senior design section of the page. Here, each requirement will be stated and comprehensive results will be shown for each requirement. In the report, video links can be given to show that "this requirement can be confirmed as successfully met here". see Zach's smart water faucet as a good reference for these past two notes. All components of the report should be written in past tense, so be careful about using content from the proposal report as that was written in the future tense. Do code appendix same way as previous, engineering standards, survey, big information like datasheets and stuff Fix chapter numbers and such in the report. New CAD assembled design is not required as we have the actual product, compare it with the old CAD design to show how it has changed and such, as well as include explanations as to why. No headings should be indented except when in the table of contents. Discuss that the survey was conducted last semester to determine the feasibility of the device, and briefly display the results. Shouldn't be as big of a talking point as it was last semester. Chapter 2 things of the proposal report will be moving to chapter 1 of design report. Chapter 2 will retain power budget, however. Engineering requirements and engineering specifications, as well as block diagrams are examples of things that will move to chapter 1 of the design semester. Deliverables for next week: The final design must be done by next meeting. Test each requirement, make videos so that we have proof that we can put onto the website

Meeting started at 1:01pm Presentation notes · Room 239 · Slide 6 might be too small (project description or whatever) · Reduce font size for titles. · Resize engineering specifications slides to fit in the respective block diagram (just that block). This will also reduce slide count for block diagrams. · Final testing and results need to be shorter, as bullets. No paragraphs in the presentation · Remove the surveys as they were done in the proposal semester. We can verbally mention if we’d like · Power budget is too small · Expenses includes repeat purchases, cost is just the price for one build. Also mention the budget from last semester compared to the expense and cost of this semester. Verbally explain why the expenses were more than the cost · Don’t need to do codes and standards on the presentation. · 30 minutes for presentation. Most of time should be on contributions and demonstration/results. Concluded at 1:31pm

Meeting 15: Start 11:03am End 11:39 am Appendix should have just A1 not Appendix A1 Covered chapters 1, 2 and 4 approved. Chapters 3, 5, and appendices need to be finalized Make sure to include more photos for the report and finalize prior to the deadline at 11:59pm Friday Start working on powerpoint presentation and have a semi completed draft prior to next meeting Next meeting on Wednesday next week

Meeting started at 1:01pm Presentation notes · Room 239 · Slide 6 might be too small (project description or whatever) · Reduce font size for titles. · Resize engineering specifications slides to fit in the respective block diagram (just that block). This will also reduce slide count for block diagrams. · Final testing and results need to be shorter, as bullets. No paragraphs in the presentation · Remove the surveys as they were done in the proposal semester. We can verbally mention if we’d like · Power budget is too small · Expenses includes repeat purchases, cost is just the price for one build. Also mention the budget from last semester compared to the expense and cost of this semester. Verbally explain why the expenses were more than the cost · Don’t need to do codes and standards on the presentation. · 30 minutes for presentation. Most of time should be on contributions and demonstration/results. Concluded at 1:31pm