Week 11 Meeting

Meeting 11: 4/2/24 (1-2:34)

• The paper is due on the 12, so the next meeting will be the last time to review it.

• The website will go live after this meeting, at 9pm, to ensure everything is up to date.

  • All table changes should be fixed on the website and in the report.

• Deliverables

  • The website should be up to date and ready to go live.

    • Fix any grammar or clarity issues in the Tables.

    • Create a separate table for individual responsibilities for the project, in the engineering specifications tab.

    • Add the cost of blinds to the budget.

  • The report is due on the 12th.

    • Ensure the table of contents is completed and up to date.

    • Add intro paragraph and responsibilities table to report.

    • Adjust CH 2 layout.

      • Move MCU paragraph to sensors section, talk about limitations in testing section, and talk about the app, its flow chart, and basic program in software section.

 

 

Week 10 Meeting

Meeting 10: 03/27/24 (11:01–12:46)

• This week quick look over the website and report were done.

• In engineering specifications - the manual mode explanation should more specific about degree of movement.

• Still need to make flowchart for software, modular diagrams

​

Engineering Specification Chart

• we should consider making another table for the responsibilities of each group.

• Battery info: wrong wording was pointed out for; table makes it sound like solar panel is the primary source of power and not battery.

• Solar Panel info: also mentioned back up battery, which is incorrect assumption

• we were advised to not abbreviate words such as. Temp -> temperature

• for components: sensors should explain their capabilities, why we’re using mentioned sensors and what’s the criteria we’re looking to measure. Not basic explanation of what the sensor is.

• for temperature sensor: “temp sensor shall measure temperature in the room in order to keep blinds at user preference.”

• sensors should include voltage/ current use

• Bluetooth module should mention which version is used, i.e., 3.5, 4.0, etc.

• Rename: Bluetooth module -> Communication Module

• Should use electromechanical module for motor/ motor driver

• motor & motor driver: should include specifications of motor needed, current/ voltage, minimum step size of motor

​

REPORT:

• intro needs to have a catchy intro sentence, talking about how your project will help in everyday tasks. Solar panel use should be mentioned in the intro.

• Survey Results should be last in CH1 of report called: Proposed Project Survey

• Rendering of the project needs to be added

• Add all survey questions to Appendix

• CH2 should be fixed

• 2.1 is a copy/ paste of project intro

• components should have better explanation.  

 

​

Week 9 Meeting

Meeting 9: 3/12/24 (1:05-2:14)

• Engineering requirements table

  • Explain angle of what for manual mode.

  • Incorporating should be lowercase.

• Custom mode:

  • Make clear what preferred means, able to adjust blinds angle.

  • Temp is a set specified temp range based on light flowing through window.

• Block Diagram

  • Add block for app communicating with Bluetooth module.

  • Add block for incident light.

• Deliverables

  • A specification table needs to be made, mentioning what’s required of each component and justification for why. Also add who is responsible for each component working.

• Module block diagrams.

• All sources should be in IEEE format and referred to on the website when needed.

  • In the proposed ideas when an idea was researched.

  • In the progress log when someone says they researched something.

• Fix timeline as it’s a proposed timeline for next semester.

  • Weekly timeline

  • Gantt timeline

• Add budget tables.

  • Fix progress log as image was moving and blocking text.

  • Fix formatting and size of tables as professor was changing zoom to be able to read.

 

​

Week 8 Meeting

Meeting 8 3/5/24 (1:05-2:28pm)

• home page

• Grammar check home page

  • Provides (not provide)

• Engineering requirements

• For each requirement, mention the number of tests and what you are testing for.

  • For each mode, specify its exact functionality.

  • 1st requirement

    • What does optimal lighting mean?

    • Look into preferred illumination in room ppl prefer.

  • 2nd requirement

    • How are we testing the app, as not stated in engineering table.

    • Manual mode should be 2 buttons and not a slider for simplicity.

• Auto mode (2 versions)?

  • 1. focus on letting a certain amount of light in the room

  • 2. focus on regulating the room’s temperature by reducing sunlight

    • entering the room. (Move to custom mode)

      • Eco mode

        • Should be removed.

    • Customization mode

      • Should allow users to select times to open blinds.

• Other

  • Add Reference page and remove timeline.

• Research

  • Sensors

    • What is their distance of reading?

    • How do they read data?

    • What angle should they be at to accurately read the ambient light of the room.

• Deliverables

• Update website & Specification table with above critiques.

• Start on lab report.

 

​

Week 7 Meeting

2/27/24 meeting (1:18pm – 2:30pm)

• Compare our project to solace and the voice-controlled blinds projects done previously.

• Redo engineering requirements, making sure everything is stated clearly and concisely.

  • 1st high priority should be the automatic control of the shutter blinds based on ambient light in room and incident light outside window.

  • Only mention the temperature sensor if that’s going to be part of the main project, i.e., working in tandem with the photo sensors.

  • For each requirement, list what test/trial will be performed and how many times.

  • Using the app to set custom preferences is a high-level requirement.

  • How the battery will be recharged is high level.

  • Solar power is a low-level requirement.

  • Conduct a survey aimed at a domestic audience, since this product is targeted at the residential audience.

• Survey can be online.

• There should be open-ended and choice-based questions.

• Deliverables:

  • Make sure the website is now updated since we have a topic.

• Add home page, all necessary tables, information related to the topic like research and requirements.

• Other:

• Try to get app set up and working by end of semester.

 

​

Week 6 Meeting

6th weekly meeting (10:35am – 11:55am)

• Two new ideas were proposed and conversed: pet feeder and automatic blinds.

  • After some discussion about the first proposed idea, the pet feeder project was deemed as a good project overall. This project has some similarities to previously done projects, but had additional features added and was tailored for cats. Some concerns were brought up about the project: is the scale to weigh the pet necessary and how will this data help identify the pet. It was noted that the accuracy of the scale may not be as accurate as needed and cats with similar weight can pose an issue. Recommended to use camera to identify the pet, in conjunction with RFID tags. Recommended to use Bluetooth to upload customer pet images for recognition.

  • The second proposed idea was smart blinds that let in certain amount of light into the room, the project was deemed to be a good project as well. The blinds should have an LCD screen for desired blind angle, use rechargeable battery to power the entire device, and provide variety of customization for users to choose from. High level requirements were discussed: LCD screen, customization, rechargeable battery. Low level requirements: phone app, adding solar panel on top of the window. Students were tasked with doing further research and come up with different level requirements, parts/ sensors used, project modular block diagram, put all research together.  

 

​

Week 5 Meeting

5th weekly meeting (1:03pm – 2:15pm)

• Further research into Glass Door Opener and Color Coder was looked over.

• Glass Door

  • The idea was turned down, citing there is a lot of products out with nearly identical features. Since there was little improvement, the idea was turned down and a different idea should be used. The wording in writing ideas should be changed, should use “shall” not “should.” Ex: ‘Glass door shall grant access to authorized persons.’  

• Color Coder

  • Component names should not be mentioned in engineering specifications. Writing what component shall do, do not specify cost (that’s a different section). When looking into success rate, at least 80% success rate should be minimum (not 60%).

  • Some concerns brought up: how to tell color of object in dark room, headphones should be low requirement, how would device respond to multiple colors.

• Tasked with finding better application for this device (not just clothes).

 

​

Week 4 Meeting

4th weekly meeting (1:02pm – 2:18pm)

• Idea 7 – Smart Garden

  • Professor mentioned the idea is too similar to previous student’s design. With further inspection and questioning, the idea was rejected due to similarity to previously built project and the idea was too simple for what was already accomplished.

• Proposed Idea 8 – Color Recognition Device for the Visually Impaired  

  • The professor was interested in the idea of a visual aid. He expressed concern with how complex this idea might get and how accurate the device may be but encouraged further research. The professor wants us to determine the scope and requirements of the project, investigate different sensors to use instead of the APDS9960, come up with an implementation plan, and a detailed description of how the project will work.

  • Concerns/Questions:

  • Is the device for those born blind or lost their sight later in life?

  • How will the device detect color and relay the information to the user?

  • Does the device need to touch an object to detect color?

  • There are multiple sensors with the code available already, how will this project be more than just purchasing one of those?

• Proposed Idea 9 – Automatic Patio Glass Door

  • Deliverables on this project are a list of required materials, an implementation plan, and project requirements.   

  • There were a few things the professor liked about the idea. The fact that the locks are connected wirelessly to the motor and the different sensors will make this system helpful for parents and the elderly. The sensors allow the door to stay closed when kids approach the door unsupervised.

  • Concerns:

    • The automated door system exists already (Publix)

    • Working on the mechanical aspects will take too much time.

    • If the system can work on any door.

 

​

Week 3 Meeting

3rd weekly meeting (1:06pm – 2:35pm)

Went over website information:

·         Time & Effort of each person, Progress Log, Weekly Meetings, Project Ideas (3 new / improved ideas).

o   Weekly Meeting section had restricted access to public and was fixed during meeting.

Discussed new proposed ideas (ideas: 4-6)

Idea-4: RFID Locked Door Powered by Piezoelectric Mat

·         Concerns:  

o   How the charging mat would be powering the door lock.

o   Can power harnessed be sufficient enough to open the door lock.

o   Is battery necessary for door lock.

·         Tasked with further research on piezoelectric devices and their current implementations.

o   Possibly combine piezoelectric with wind/ solar power generation.

Idea-5: Sus-taina-Street Lights (Revised)

·         Idea was identical to previous proposed idea; difference was not significant and was promptly rejected.

·         Revisions were only complicating the project which will not have a significant impact to designs currently in production.

·         The proposed addition of sensors was not practical since exact data is available on weather station applications.

Idea-6: Portable Hybrid Power System

·         Idea was recognized by professor, with several questions in mind, idea is still in discussion.

·         Were tasked with providing some calculations of capabilities of the battery and longevity of provided power.

·         Some of the questions asked of us:

o   How high should the wind turbine be to provide steady charge.

o   How will generate power be stored in battery.

·         Tasked with looking into charging battery using with AC wall charger for longer use.

·         Research specific applications the power source would be used for and how long it should last.

·         Should look into DC-to-DC converters for specific charging.

·         Calculate full charge and discharge of battery.

o   Full charge on solar/ wind

o   Full charge using AC wall outlet  

We were instructed to look at different projects within the electrical engineering field.

·         Instructed to select a more useful and not redundant project.

 

​

Week 2 Meeting

2nd weekly meeting (1:03pm – 2:13pm)

• Went over the website and 3 ideas proposed.

• Website:

  • Recommended: changing background color on some tabs as the text was hard to read, fix minor layout issues, and rework Time and Effort.

  • Weekly meeting had restricted meeting by mistake and was fixed before the meeting

  • Time and Effort table was hard to read / follow and should breakdown by each person contribution. Suggested setting up rows for each person / group and column set for each week.

• Proposed Idea 1: Portable Wind-Solar Water Purifier

  • The idea was recognized by the professor

  • But due to complexity of purification process, idea was rejected

  • With our limited understanding of how to make water drinkable, how will we know the water is safe for consumption, and lack of wind energy production in most conditions where the product would be used.

  • On ground level, the wind harvested for power would not be great enough to incorporate into the project.

• Proposed Idea 2: Portable Energy Harvester

  • The idea was recognized by the professor with some uncertainties

  • Due to low power produced from piezoelectric devices, the idea was rejected

    • Voltage produced through piezoelectric means is acceptable, but current produced is in very small (milli or micro amps).

    • Thus, not enough power produced to charge a device.

• Proposed Idea 3: Sus-taina-Street Lights

  • The idea was recognized by the professor with some uncertainties, the idea was rejected

  • Uncertainties were brought up for where to implement the street lights, wind production issue, simplicity of the project.

    • Issues brought up with:

• Most areas are not going to produce sufficient wind power to produce power

• Battery size and storage of it was brought up

• Will solar / wind be enough to power the LED for 12 hours

• Typically, LED street lights come equipped with motion and photosensors built-in

• Proposed idea would be too simple for group of 3

• Nearly identical idea is currently in production and for sale by a company

  • *Each proposed project had minor issues with block diagrams which needed to be addressed.

• We were asked to add more ideas for this idea

  • 3 proposed ideas were rejected and we were tasked with coming up with new ideas or modifying current ideas for next week.

 

​

Week 1 Meeting

1st weekly meeting (9:02 am – 10:43 am)

• Established what needed to be done by the next meeting.

• Websites should have a time and effort tab, meet the team tab, progress log, weekly meetings tab.

• 3 proposal ideas, each with a general description, functionality, marketability, block diagram and comparison table if applicable.

Briefly went over requirements for the final lab report and presentation.