
Week 6 - Fri 06/14 - Fri 06/21 (1:45 - 3:00pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​
General Ideas:
-
Use a common font between all pages.
-
Alter diagram backgrounds to be more readable.
-
Update flow charts with decision blocks to distinguish them from block diagrams.
-
Reduce the language under the product description.
-
Update final block diagram/flowchart
-
Numerous updates and rearrangements of the engineering requirements and specifications tab.
-
Update progress log with individual and group contributions.
-
Professor Notash recommended we meet with Dr. Javier Garces to discuss the agricultural part of our project.
​
Action Items:​
-
Update the professional look of the website including fonts, spacing, colors, etc.
-
Update the design requirements with more information on the system hardware, functionality, and critical system requirements.
-
Update the language on the website to be more concise.
-
Finalize the physical design of the system.
-
Contact Dr. Javier Garces.
-
Begin/continue work on the proposal report.
Week 5 - Fri 06/07 - Fri 06/14 (1:15 - 2:50pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​​
General Ideas:
-
Increase specificity of requirements and specifications
-
Flip requirements hierarchy
-
Design circuit for power budgets and perform analysis
-
Provide project dimensions on the website
-
Ensure the abstract is immediately visible upon opening the website
-
Abstract: short paragraph followed by bullet points on what it does
​
Action Items:
​
-
Final Proposes Ideas & Diagrams
-
Change Domain Name
-
Change summary to Descriptions
-
Move title proposed to one
-
Change background of drop down menu
-
Change the main menu abstract to short summary and 3 functioning points
-
Come up with a catchy name
-
Fix the power budget to meet the demands of our design
-
Change "summary" to "project description"
-
Add details to marketability and budget
-
Time and effort table is a live table that must be a part of the website
Week 4 - Fri 05/31 - Fri 06/07 (1:00 - 2:45pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​
Requirements
-
Weight and Dimensions - Clearly state the weight and dimensions of the device.
-
Target Audience - Determine if the device is designed for indoor or outdoor use, and if it will be used in areas with easy access to outlets or more remote areas.
​​
User Identification
-
Quick User Identification - Quickly determine who the intended user is.
​​
Construction Method
-
Build vs. 3D Print - Consider constructing the device ourselves instead of 3D printing it.
​
Material Selection
-
Material Consideration - Use plexiglass to allow visibility inside the device, but assess potential heat retention issues.
​​
Website Content
-
3D Rendering and Purpose - Include 3D renderings and clearly state the purpose of the project on the website.
-
Main Functions - List bullet points of the main functions of the device.
-
Device Design Renderings - Move current device design renderings below the initial rendering without splitting the abstract.
​​
Banner Design
-
Background Brightness - Make the background as bright as possible to avoid dark backgrounds, which are less preferred by panelists.
-
Professional Appearance - Use light/bright backgrounds for a more professional look.
-
Font Size - Ensure the minimum font size is 14.
​​
Power Budget Assessment
-
Create a circuit to determine a design power needs.
-
Power Source Decision: Decide whether to use a solar panel or battery pack based on the power budget assessment.
​
Action Items:
​
-
Landing Page - Create a proposal tab with all our ideas typed in, not as pictures.
-
Block Diagram - Insert pictures and hyperlinks into the block diagram.
-
Website Source - Right-click the website and look at the source for reference.
-
Design Requirements - Upgrade design requirements with specificity, such as voltage and current requirements. Look at CNC design requirements for reference, and include pictures and hyperlinks.
-
Success Criteria - Clearly define success criteria that tie specs and requirements together in the test trials.
-
Dimensions and Material - Specify the dimensions, material, and weight requirements, and input them into the website.
-
Weekly Meetings - At weekly presentations, list the latest week at the top and the oldest at the bottom.
-
Time and Effort Table - Include a time and effort table and a progress log.
-
Budget - Include the cost of vegetation, target specific vegetation, and the environment growth height we are looking for before transplanting outside.
-
Documentation - Start working on the document soon, with a template available in Canvas.
-
Project Goals - Be clear on the goals of the project.
Week 3 - Fri 05/24 - Fri 05/31 (1:10 - 2:40pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​
Charts and Analysis
-
Provide charts showing the involvement of hardware and software.
-
Include percentages for hardware and software contributions.
-
Sensor Data:
-
Measure sensor data to produce charts of historical data.
-
Keep data for 1 week and log it in an Excel sheet.
-
Graph data versus time.
​
User Interface
-
Develop a user interface attached to the system for visual display.
-
Create a user app for remote access and control.
​
Portability​
-
Ensure the system is portable.
​
Fluid Management
-
Design three pipes to release a premixed solution and clean water when levels are low.
-
Aim for maximum autonomy, especially in mixing fertilizers without user intervention.
​
Task Performance
-
Detail how each aspect of the system will perform its required tasks.
​
Engineering Specifications
-
Focus on the requirements of the design rather than the components being purchased.
​
Research and Inspiration
-
Review the CNC machine Senior Design Project for insights and inspiration.
​
Action Items:
​​
-
Engineering Design Requirements
-
Success Criteria:
-
Ensure trial types have 20-30 trials for sufficient data.
-
Specifications
-
Rendering
-
Website
-
Preliminary Report
Week 2 - Fri 05/17 - Fri 05/24 (1:00 - 2:30pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​
Good Ideas
-
Nail down the final idea.
-
Determine which idea you are most passionate about.
-
Define the scope of the project.
-
Establish minimum and maximum functionality.
​
Sanitizer Bot
-
SMART Goals:
-
Specific
-
Measurability
-
Achievable
-
Realistic
-
Timely
-
-
Determine the robot's height and how it can reach the center of tables.
-
Narrow the scope.
-
Recognize that building the robot could involve more mechanical work than electrical and computer.
-
Consider buying the base and creating the arm for it.
-
Use infrared or other technology to image doorknobs before and after sanitizing to detect pathogens and measure impact.
​
Seedling Care Center:
-
Implement a floating NPK sensor.
-
Focus on plant control and care.
​
Item Robot:
-
Maintain a very detailed log of items.
-
Review and improve upon similar projects done by others (3 or 4 projects).
-
Consider moving away from mechanical aspects.
​
General Ideas:
-
Maybe include a camera in each project.
-
Next slide presentation should focus on SMART goals.
-
5 slides, one for each aspect (Specific, Measurable, Achievable, Realistic, Timely).
-
​
Action Items:
​​
-
Implement SMART for each proposal idea
-
Add detailed
Week 1 - Fri 05/10 - Fri 05/17 (1:15 - 2:50pm)
Attendees: Jonathan, Deven, Professor Notash
Discussion:
​
-
First meeting with Notash
-
Went over syllabus
-
Next meeting Friday at 12pm
-
$600 budget
-
8 months
-
Use 14 Font
-
Power Point (proposal ideas)
-
Proposal Ideas.pptx
​
Action Items:
​​
Project Tasks
-
Both team members sign the contract and send to professor.
-
Document each person's contributions.
-
Organize tabs on the website.
-
Main page should feature an abstract/explanation and project motivation.
-
Discuss all design ideas.
-
Record minutes of weekly meetings with the professor.
-
Develop a block diagram with explanations for each proposal idea and its components.
-
List citations and references used in research and design implementation, with reference numbers in squared brackets.
-
Email the professor project ideas for the next week's meeting.
-
Maintain a progress log.
-
Record meeting minutes with the professor.