top of page

Weekly Meetings

Week 11:

Weekly meeting: 07/16 - 07/22 (12:03 - 1:42 )

  • Flowcharts need titles on the website to tell them apart

  • Proposed Budget (not Expense on Website)

  • Actual Expense (all it took to build the project)

  • Project Expense (what it took to make the project)

  • Testing needs videos linked (embed the videos from Youtube)​

 

​Report: 

  • Abstract looked fine

  • Page numbers need to be updated in Table Context 

  • Multiple figures in report need (a) (b) reference 

  • Hardware Development 

  • How project was built not the components that were changing

  • Changing of components is troubleshooting 

  • Section 3.2

    • 3.2.1 - Hardware - physical build of the system

    • 3.2.2 - Sensor - Physical build build for the system

  • Troubleshooting - mention that two BLE modules couldn’t be integrated 

  • During presentation - 1 slide talking about issue implementing 2 BLEs & mention why we went with hardware approach 

​​

Next Week Deliverables: 

  • Finish report and submit Friday

  • Final review of Presentation

​

​

Week 10:

Weekly meeting: 07/11 - 07/15 (12:20 - 1:54 )

Work on manual mode to see if at least 6 timers can be received 

  • Report : 

    • ​Changes and revisions needed were written as we talked throughout the meeting

    • Title is BSECT

    • Abstract  

      • Use present/past tense not future

      • Add 2nd paragraph explaining different modes of operation (should not exceed 1pg)

    • Ch1

      • Needs survey questions like proposal 

      • Responsibility table should be here too 

      • Intro

        • ​Survey should like with motivation 

        • In motivation, talk about survey & doesn’t have to be separate header.

      • Project requirements 

      • Pictures don’t have Fig# and some are mislabeled 

      • Fix block diagrams 

      • Table comparison after similar products/ projects 

    • Ch4

      • ​Expenses not budget

      • Expenses (project expenses vs actual expenses)

    • Take out anything pertaining to temperature sensor 

    • Sensors should be italic

    • Solar panel only, don’t need history or different kinds

    • Ch3 - project contribution 

    • Talk about how you did the project (your original contribution)

    • Final design is part of build phase 

    • Ch4

  • Revise what parts were used for the project, prototyping should not exceed $500.



Week 9:

Weekly meeting: 07/02 - 07/10 (12:00 - 1:11 )

  • Discussed auto mode & BLE connection test issues

    • Proceeding with physical attachment of BH1750 light sensor

  • ​Look into hibernation

    • Have it check selected closing time is greater than current time and blinds are in closed position

  • ​Report:

    • Survey questions are part of ch1 still

    • Organize report by rubric 

  • Test Auto mode

  • Work on report

​

​

Week 8:

Weekly meeting: 06/25 - 07/01 (12:30 - 1:10)

  • Updated block diagram to new version (looks good)

  • Engineering Specifications fixed (looks good)

  • Have manual mode go from 0-180 degrees

  • Make note of any troubleshooting being done. (how you did something & what you did to fix it.)

  • Deliverables: 

    • Make sure data is sending/receiving properly on sensors

    • Incorporate sleep mode into both room and window MCU

    • Manual mode should be fixed and working 

    • Manual/ Custom mode operation should be thoroughly tested

    • Implement new solar panel

​

​

Week 7:

Weekly meeting: 06/18 - 06/24 (12:01 - 12:31)

  • Update block diagram to new version 

    • Use Jordan’s diagram (fix diamond boxes to regular boxes) 

  • Fix:

    • ​Power Distribution

    • Electromechanical Diagram 

    • Engineering Specifications (charge controller should be taken out) 

    • Engineering Requirements (fix lumens -> lux, and wording of AUTO mode)

    • Update Time/Effort 

  • ​Deliverables: 

    • Manual mode should be fixed and working (where UP mode was not working correctly)

    • Manual/ Custom mode operation should be thoroughly tested.

​

​

Week 6:

Weekly meeting: 06/11 - 06/17 (12:01 - 12:52)

  • Fix Home Page to include: motivation/ need for choosing the project, followed by explanation of the project

  • In Engineering Specifications:

    • In power Module, include:

      • Boost Converter 

      • Solar Power charger

  • ​​Sensors:

    • What’s the range: Voltage, Current, Light requirements for project

  • ​References:

    • ​Should be updated

    • Take out -> report references 

    • Separate the references by Proposal / Built phases of report

  • ​App chart: 

    • Current Time -> should be rectangle 

    • Modes Selected -> should be rectangle 

  • ​Deliverables: 

    • Update website with above

    • Jordan/ Vasyl

      • Test manual/ custom mode with motor and blinds

      • Combine motor code/ main code

​

​

Week 5:

Weekly meeting: 06/04 - 06/10 (12:10 - 1:11)

  • Home page

    • ​Needs catchy phrase to get audience attention 

    • Few paragraphs of need and motivation for the project

    • Have pictures of how blinds will look as completed product

  • Phone App diagram

    • Fix: AUTO mode (still has current time variable)

  • ​External Sensor

    • Look into adding button to turn off device

  • ​Flowchart

    • Counter should not be 60k 

    • Look into interrupts to wake up from 20 min timer

    • AUTO can be combined to single function

  • ​Engineering Requirements:

    • replace : Lumens -> Lux

​

 

Week 4:

Weekly meeting: 05/28 – 06/03 (12:01 – 1:32)​

  • Flowcharts need to be modified

    • Default_Auto -> Default_AUTO_MODE

    • Fix if else statements in charts, where is condition is met, the program goes to next task

    • Timer_Mode Taken out and included in AUTO_MODE

  • Room Sensor

    • Use 1 sensor, no need to use 2

  • Mechanism to manually open blinds is not needed

    • Should document it as future improvement

  • App:

    • Fix CUSTOM string to send 1 input at a time

    • Save/ process variables time, modes, custom

​

​

Week 3:

Weekly meeting: 05/21 - 05/27 (12:02 - 12:59)​

  • Fix:

    • Update software flow charts

    • Custom table

      • Make sure it is clear that the user needs to specify start and end times, as well as specific degrees the blinds should be at.

    • Deliverables:

      • app should be done 

      • Ambient circuit should be assembled and tested.

      • Issue with motor adjusting the blinds for a max of 30 degree should be resolved

​

​

Week: 2

Weekly meeting: 05/14 - 05/20 (12:01 - 12:49)

  • Fix:

    • Engineering requirements 

      • Fix wording: consistently —> periodic adjustments (15-30 min)

      • Remove: “time” from Custom mode and remove bulletin. 

    • Put table of responsibilities as separate tab on website 

    • Title for budget should be “Project Expenses” and no table heading

      • in project expenses tab: have proposed expenses vs actual expenses 

    • Weekly meeting: have white background & larger font. 

    • Blog should only have 1 post per person for each week, not multiple =.

    • Deliverables:

      • app should be 90% done (custom mode) 

      • sensors should be working/ taking measurements 

      • look for battery to use for main and secondary microcontroller  

      • Trim blinds 

      • have motor attached to housing

​

​

Week: 1

Weekly Meeting:  05/07 - 05/13 (12:02 - 1:01)

  • Website format is similar as before: meeting effort, progress log

  • Charts will stay the same as design phase of project, with suggested modifications

  • Temperature sensor will be taken out

  • Website should be up and running / everything posted on it

  • Flow charts should be redone and posted by next week

  • Requirements should be updated

    • Keep solar panel as low LVL

    • Take temperature sensor out

    • Put delay of blinds movement to: 15-30min

  • Arduino should read increments, not constantly

  • Have user input lumens value

    • Think of range: 500-2000 lumens

  • Combine rechargeable battery with solar panel 

  • Charge from level to priority level in engineering requirements 

  • Or write a footnote on bottom of engineering requirements what each priority LVL is

    • High - without it, project will not be successful 

    • Low - without it, project will be successful 

  • Ambient light sensor should be in middle of room sending data through Bluetooth/ RF

bottom of page