- No Meeting -

Meeting 1: Wednesday, 5/14/2025 3:45pm - 6:06pm We had our preliminary meeting with Dr. Ejaz regarding becoming familiar with the senior design proposal course, what is to be expected of us moving forward, as well as discussing our first proposal ideas. Moving forward, a short meeting synopsis will be provided first here, followed by the notes taken during the meeting. Note that items highlighted in blue are deliverables discussed in the meeting, and items highlighted in red are critically significant pieces of content. Discussed new meeting time (Wednesdays at 10:00am) Meeting link added to class page Presentation important notes When starting and pitching proposal, make it absolutely clear what exactly it is we are planning to do 20 minutes long, 2 sessions ran in parallel (Ejaz students in one session, around 3 projects and 1 proposal) 2 to 3 panelists/judges per session Project report important notes 65% of grade Easy to make and write if progress log is very detailed NEED TO MAKE OURS MORE COMPREHENSIVE Do not ignore collection of references, start doing this now Website important notes ADD LINK OF REFERENCES This goes next to the tab which says senior design Usually at least 3 items updated every week, such as minutes and progress log. Group grade by the above three things will be scaled by teamwork and leadership evaluation, i.e. if one student works less, their personal grade will be scaled down. Presentation day is Friday July 25th, The final proposal report is due July 18th Landing page must should not have the final idea placed until project is decided Website says proposal timeline, should say project timeline, no proposal tasks included in the timeline, rather it would have how the project steps will be implemented in the form of a Gannt chart, weekly tasks and such. This timeline will be created during the proposal semester. This will be compared with actual implantation timeline which occurs during design. Add survey link in proposals drop down for surveying target audience for product Block diagram page will only have the final idea, move current proposals to the same proposals pages ParkSense LiDAR may be overkill for this implementation B-CAN Maybe make glasses with band at the back instead of headband BTL Is it doable Take sampled data and try to Bluetooth transmit to another device Remove any mention of discerning specifics such as hostiles or friendlies Be careful about choosing application Re think the application of this, there are issues with the two current applications with this Block Diagrams Modular Engineering specifications Meeting 1 Deliverables:​ Two potential projects BTL Figure out applications B-CAN Maybe transitioning to glasses approach rather than headband Make website adjustments Time/effort, progress log, survey link, block diagram page, landing page, timeline

Meeting 2: Wednesday, 5/21/2025 10:00am - 11:30am Our second meeting with Dr. Ejaz allowed us to hone in on a final project idea, that being the B-CAN glasses idea. We discussed the non-complexity of the refined BTL idea, and determined that moving on from the idea was best. We also discussed more general senior design deliverables, as well as began discussed what would be needed for getting started on B-CAN. Checked the website to start before getting into discussion items Proposal timeline should be changed to “proposed (project) timeline”. This means that the proposal content will not have a timeline, rather a plan will be made for the project’s timeline. Then in design, there will be an actual timeline which is created as work is completed. Time & Effort page needs a “group” tab, as a third column. This will have content which was conducted together, such as building or testing the project. ABET wants to see students who are able to lead an engineering project, as well as work in an engineering project as a team. Progress log is an expansion of Time & Effort, and should also have a group column. Pictures, videos, and other types of content can be included in this section, but it should be more comprehensive. Discussed feasibility of new BTL project idea Bluetooth for this project may fall under future recommendations if we “maybe” plan to do it with time Need to update the block diagram as well Hardware is fairly straightforward, battery to MCU, then MCU to LiDAR Overall pivot to the B-CAN idea 360 degree Shouldn’t have battery touching eye Old project was too heavy and wasn’t comfortable to wear Monetary budget should include optimal budget, as well as repeat purchases for things that break or are lost. Proposal monetary budget should be how much is planned to be spent. Specification table should include pins used, frequency of MCU, etc… SURVEY IDEAS How often do you utilize a device with haptic feedback in your average day Do you prefer audio or haptic feedback on personal devices? For a device which aides in your environmental navigation, would you prefer audio or haptic feedback? Need “motivation” for the project Could do a test with a phone with eyes closed, walking with vibration on phone and audio when to stop Meeting 2 Deliverables:​ Proper block diagram for B-CAN (system and modular block diagrams) System shows how system is created Modular shows what modules are there and what is the function of each Software flowchart, show flow of everything software wise Set requirements for the B-CAN project System shell capabilities (what can it do, who is it for, other characteristics of system) Description of the problem (existing solutions first, then our proposed solutions) USE SHELL AS IT IS PER STANDARDS Set success criteria Target audience for survey soon (after above things are set) CAD Drawing of idea Fix Home page to reflect new idea

Meeting #3: Wednesday, 5/28/2025 Meeting Started at 10:00am Maybe change B-CAN name to better reflect the project Don't say that it is head mounted if it is going to be a pair of glasses with a headband in the back Notably, this can be found on the main home page in the Our Solution section QUESTION Under existing solutions section, including photos of existing products? ANSWER Needs to be a comparison table/chart, can include photos in this chart if desired Comparison table should go after Our Solution Write down what any pictures or videos or any figures are about, never offer without context (even a single sentence is sufficient) Include color key for red and blue arrows on the block diagrams User interface needs only two buttons, the mode select may not be useful and could be a waste of time to implement Power budget should be low for this project, as the sensors and haptics are all low power devices. Maybe use the haptic motors to determine power level rather than the speaker This is to try and reduce the overall weight of the device For example, four vibrations for full battery, two for half, one for a quarter In Engineering Requirements Be clear for things such as what accuracy means; How far? Offer measurable data What is goal first? Then we can choose sensors after that based on the use case. Health and Safety concerns, no electrical shock risk or exposure to dangerous components to the person Low voltage/Current etc… Heat dissipation No requirements should say actual devices, such as specific MCUs. Instead, requirements should say what we want out of the MCU such as clock rate, latency, etc... For the survey, ask the blind community what distance they would want to be alerted, such that it acts as a solid reason to add a distance to the engineering reqruirements System requirements, typo which says maximum latency, make it say minimum latency Survey Stuff Survey must be accessible in some way Don’t include questions like “Do you prefer haptics or audio” since we are going to be using haptics. Change stuff that says head mounted, make it say glasses At some point, introduce the device in the survey, people need to know what it is they’re being surveyed for CAD drawings should have dimensions and for different angles, 3D rotatable models on the website if possible Meeting 3 Deliverables: First iteration of Engineering Specifications done First iteration of flowcharts must be completed, including software if applicable Survey must be fixed, and some method of making it accessible determined CAD drawing if possible Block diagrams need to be fixed for second iteration Home page fixed with comparison tabnle at the end Any tabs which are not completed should be completed whenever possible Meeting Adjourned at 11:09am

Meeting #4: Wednesday, 06/04/2025 Meeting Started at 10:10am Reviewed new home page changes, all looking good Be careful calling it a headband, use the term glasses instead, like swimming glasses Change this in the comparison table Add data sheet for Raspberry Pi Pico 2 to References On that note, the Raspberry Pi Pico 2 looks good to move forward with Progress log must reflect group work, similar to the time and effort log This is very important, as it is part of the ABET criteria for Valencia Change the format of the progress log, such that there are two individual columns for both Laz and Ant, then below there would be a centered group work column Monetary budget can be started, we need to start choosing components. Create a table and start filling out as we select more components. Engineering Requirements changes Number 7 system shell is not a requirement, so maybe remove There should be no exposed surfaces of system to wearer (glass should be safe to operate) Change 120 degree to 360 degree Exchange positions of numbers 4 and 3, weight is more important than battery charge Temperature should not increase beyond ambient temperature Engineering Specifications changes Don’t include things like voltage divider, as it is a circuit, not a component Include capacity and dimensions of batteries, how long it will last Don’t give exact name of components, just the requirements we need out of them For example, don’t say “Sharp IR Sensor”, say “100-500cm range IR Sensor” ADC requires how many bits, what is the reference voltage to determine step size Communication interfaces should go in MCU part Voltage regulator in power module may be required to boost power to MCU, to ensure pins are receiving at least 5v (or whatever we settle on power wise) Later discussion proved that we do need a boost converter of some sort due to the high supply voltage requirement of the SHARP IR sensors Block Diagram Changes Change User Interface to just onboard When using motor driver, power should come directly from battery, and send power to the response module Also mode the motor driver to the response module, not the control module Vision module should not have ADC in it Remove Speaker, also maybe include motor driver in response module Change User interface module such that single power button for powering on device, sensors are calibrated on powering device, and hold to determine power level. Maybe option for device to provide option to modify the distance at which the feedback is provided For flowchart, change calibration state to mode select state, and add calibration to power on start Maybe remove the flash IR sensors language to “activate” IR sensors. Maybe change survey to reset question number after each section Need another tab for distribution of responsibilities See James and Francisco’s website for example Meeting 4 Deliverables: Add responsibilities tab Make sure it’s just for work performed in design semester, first iteration is fine Block diagram and Flowchart Changes Engineering Specification Changes Engineering Requirements Changes Monetary Budget can be started Add group tab to progress log Meeting Adjourned at 12:04pm

Meeting #5: Wednesday, 06/11/2025 Meeting Started at 10:01am Decided on a new meeting time for Mondays at 6:00pm Workshop for senior design/proposal set for Thursday June 26th at 6:00pm Begin on the project timeline, intial iteration due next week This is a proposed timeline, which will be compared to the real timeline followed in the design semester. Do not include anything about the proposal semester Task allocation should only include things that are part of actually creating the project, not things like website , only real implementations. For instance system programming, sensor integration, clearly define the implementation things (this, this and this needs to be done to create the project). See Jasime and David's page for a good example In Time & Effort, swap duration and description columns Weekly Meetings dates should show the days between meetings, not the calendar weeks Pictures must be taken when testing and prototyping. This would be considered actual progress. (preliminary work). Videos posted to youtube work as well Keep the motors in the prototype down to 8 motors, add 16 for future recommendations Scaling up always looks better than scaling down Resources should be IEEE format Make Weekly Meetings include a date with Week # title Monetary budget should only be for what goes into the device, do not include redudnancy orders. Include total budget at bottom Engineering Requirements Changes "The system shall" at the top so doesn't need to be repeated every row Take worst case scenario for specification data First calculate the power dissapation of the entire project before offering a "operational battery life" number. Offering backing information for any proposed specifications Operating temperature should be changed to Be careful about putting condition operations, as those conditions will have to be tested against Engineering Specifications Changes No component names (i.e. pico 2), just "MCU" with specifications needed. Should be what we need out of component type X, not specifications that component name y offers. Flowchart/Block Diagram Changes Maybe change "response module" to "electromechanical module" Move driver to this module as well from control module Change "user interface" to "input module" Talk to professor at workshop regarding input on the flowchart Meeting 4 Deliverables: Begin Project Timelines Fix Time & Effort Page Fix Future Progress Log Pages Fix Engineering Requirements and Specifications Potential Fix for Block Diagrams Fix Monetary Budget Fix Weekly Meetings (Add Dates) Meeting Adjourned at 11:37am

Meeting #6: Wednesday, 06/16/2025 Meeting Started at 3:03pm Need to have something to show for CAD model by next meeting Timeline Changes Remove CAD model, should be done in the proposal page If there are project things done in proposal semester, can include in timeline Allocation of Work Changes More project oriented, See Dylon and Steffanie's for good example Maybe no simulation (No mechanical simulations needed) Continuing to fix date structure for Time & Effort and Progress Log Engineering Requirements Changes Continue implementing WCS (Worst Case Scenario) data following testing of components Safety considerations should be no sharp edges, sealed electrical components, temperature, etc... Engineering Specifications Changes Control Module, Change Response Module to Electromechanical Module, and move motor driver from control to electromechanical Change Vision module to sensor module Block Diagram Changes Change Response Module to Electromechanical Module To avoid confusion regarding battery vibration and object vibration, design different feeling responses (such as how a phone has a short sharp vibration for a text and a lengthened "softer" vibration for a call) Power Budget Changes Boost converter might cause battery to not provide enough current when boosting voltage, might need to choose different battery. Maybe add Ah or Wh Include preliminary work in chapter 3 of report and the timeline (the start of the project implementation) Meeting 4 Deliverables: Timeline Changes Allocation of Work Changes Engineering Requirement and Specifications Changes Block Diagrams Changes Power Budget Changes Meeting Adjourned at 4:10pm

Meeting #7: Wednesday, 06/23/2025 Meeting Started at 3:00pm Showed current iteration of CAD model Explain very clearly how exactly the haptic feedback should be perceived by blind person Get information on this from survey, "Here is what we are planning, what do you think you'd prefer/is best?" Adding slots for ventilation, accommodate for rain Timeline Changes Change construct presentation to create/practice Add write report Add testing components Website Changes Add codes and standards to references Report Changes We should have the report started by next meeting. Lucky for us, it already is. List all codes and standards in appendices Continue Working on Report Add the correct one to website Power Budget Changes List if it is Nema or other type of standard (1C or 3C) Monetary Budget Changes Add even minor things such as sodlder and wire Engineering Specifications Changes Test the fast charging, but here we can put that it has the support for fast charging (just put the stock numbers) Meeting 7 Deliverables: Proof of Concept System with one motor, one sensor, and the microcontroller. CAD model updates Timeline Changes Website Changes Report Changes Power Budget Changes Monetary Budget Changes Engineering Specifications Changes Meeting Adjourned at 3:52pm

Meeting #7: Wednesday, 06/23/2025 Meeting Started at 3:00pm RED - Submission is in two weeks, so need to start filtering down our end case uses Next semester, will have actual task allocation to compare to proposed, to ensure individuals are performing their promised roles For references, there should be a standards of codes tab, and a references tab. The standards and codes should not be under the references tab. Maybe change References to More, and have both standards and codes as well as references underneath the "More" tab. Maybe include meet the team under there as well (not necessary, just a thought). Add dimensions to the CAD drawing Upload videos to youtube not directly to wix Meeting 7 Deliverables: Next meeting go over as much of the report that we can finish, by the meeting after that, the report should be almost complete. Upload videos to youtube instead of wix. Add dimensions to CAD drawing. Start working on presentation soon - Can basically create it off of the report. 20 Minutes for the presentation. Report submitted one week before the presentation. Add survey responses to website. Splitting references and codes and standards into two pages. Meeting Adjourned at 3:38pm

Meeting #8: Wednesday, 07/07/2025 Meeting Started at 3:02pm Primary objective is currently writing and finishing the report Add dimensions to at least one image, can have others without after if desired Move requirements to the top of the drop down list as it changes infrequently Finish the flowhcharts for the functions and interrupts as well, don't need to include code but need to show logic When presenting code in report, took lines which describe function or block of semantics (see david's code for example, but put explanation first then the image of the code) School of Engineering should be next line Explain very clearly that the interaction with lighthouse was for the survey in the abstract. Write exactly what was the purpose of the collaboration with lighthouse central florida. Lockheed Martin Employee mentioned specifically that he needs to explain the difference between technical and creative writing Throughout the entire report, be more specific All figures should be in the center of the report, don't creatively include them within the paragraph Combine problem statement and introduction maybe do 1.1.1 for problem statement and 1.1.2 for intro Survey questions and results can go in the appendix, just summarize and give result summary in chapter 1. Show main question results in the section. Do paragraphs for "One of the questions which greatly affected..." 2.1, remove comma in system overview give reference to figures when one is upcoming FOR PRESENTATION How are we going to connect with the audience, ask question? talk with them? make a scenario? Explain project in a way where nothing is left unexplained, it should be very clear what it is exactly we intend to do Meeting 8 Deliverables: Meeting Adjourned at 4:11pm

Meeting #9: Wednesday, 07/14/2025 Meeting Started at 3:03pm Need to add new block diagram and flowcharts to website Show hardware component, show specification on same slide, and show wher it will be used for presentation engineering specifications SEE REPORT DOCUMENT FOR COMMENTS REGARDING REQUIRED CHANGES, THERE ARE NUMEROUS Look into interactive block diagram pages Move monetary budget toward the end after timline in presentation remove the dates in the gantt chart for website, report, and presentation References should be last in presentation, right before opening the floor to questions References in presentation should only include what is relevant and used FOR the presentation Talked about some senior design aspects, such as changes to the report, expenses, and more. Continue updating progress log if working on project during break. Meeting 8 Deliverables: Report Changes Powerpoint Changes Finishing Flowcharts Meeting Adjourned at 4:12pm

Meeting #11: Wednesday, 07/21/2025 Meeting Started at 3:00pm If any statistics are mentioned in the presentation, must make verbal note of their reference Attention grabber needed at start, maybe ask for raise of hands if anyone know someone who suffers from visual impairment Don't read roadmap Add in number of sensors on the slide for design proposal, probably add even a rudimentary CAD image of the 8 sensor design Fix electromechanical block diagram to say 8 motors in presentation Make Flowcharts visible for large scale Include specific component names in specifications Label figures, especially in engineering specifications Number the references, not bullet point Meeting 7 Deliverables: Practice and finalize presentation! Meeting Adjourned at 3:28