Difference between revisions of "Lunar Agricultural Zone (LAZ)"

From EG1004 Lab Manual
Jump to: navigation, search
 
(28 intermediate revisions by the same user not shown)
Line 6: Line 6:


= Introduction and Overview =
= Introduction and Overview =
In 2021, humanity faces the problem of feeding its growing population. Currently, half of the Earth’s habitable land (51 million km<sup>2</sup>) is used for agriculture, leaving little for much else. To combat this, the United States National Aeronautics and Space Administration (NASA) has turned to <b>lunar agriculture</b>. With a surface area of over 37 million km<sup>2</sup>, the moon has the potential to farm over 70% of the Earth’s current supply. Due to the slow period of rotation, stationary crops on the moon will be exposed to 27.3 days of continuous sunlight then darkness. In order to have greater control over the sunlight exposure of crops on the moon, NASA has issued an RFP (request for proposal) for a rover capable of traversing <b>the Lunar Agricultural Zone, the newest solution to world hunger</b>. This rover would traverse the unsmooth terrains of the moon, locate various crops, and determine if they should be moved depending on the levels of light exposure detected. By keeping rigorous control of the light exposure of the crops, NASA hopes to create an environment capable of sustaining plant life on the moon.
Humanity faces the problem of feeding its growing population. Currently, half of the Earth’s habitable land (51 million km<sup>2</sup>) is used for agriculture, leaving little for much else. To combat this, the National Aeronautics and Space Administration (NASA) has turned to <b>lunar agriculture</b>. With a surface area of over 37 million km<sup>2</sup>, the moon has the potential to produce over 70% of the Earth’s current food supply. Due to the slow period of rotation, stationary crops on the moon will be exposed to 27.3 days of continuous sunlight and then darkness. To have greater control over the sunlight exposure of crops on the moon, NASA has issued a request for a proposal for an autonomous rover that is capable of traversing <b>the Lunar Agricultural Zone (LAZ), the newest solution to world hunger</b>. This rover would traverse the unsmooth terrains of the moon, locate various crops, and determine if they should be moved depending on the levels of light exposure detected. By keeping rigorous control of the light exposure of the crops, NASA hopes to create an environment capable of sustaining plant life on the moon.


The objective of this mission is to locate and <b>collect all plants</b> in the Lunar Agricultural Zone overexposed to sunlight. To complete the given tasks, either the gyro, touch or ultrasonic sensor can be used to increase the accuracy of the rover movement. After the overexposed plants are obtained, they should be transported to an area of less exposure.
The objective of this mission is to locate and <b>collect all plants</b> in the LAZ that are overexposed to sunlight. To complete the tasks, a gyro, touch, or ultrasonic sensor can be used to increase the accuracy of the rover's movement. After the overexposed plants are obtained, they should be transported to an area of less exposure.


= Specifications =
= Specifications =


Design a robot using Fusion 360 as your primary design tool. The robot must meet the following specifications:
Design a robot using Fusion 360 as the primary design tool. The robot must meet the following specifications:
*Size & Material Constraints
*Size & Material Constraints
**The robot should fit within a 12 in x 12 in footprint. Larger robots are allowed, but discouraged.
**The robot should ideally fit within a 12" x 12" footprint. Larger robots are allowed but discouraged.
**A cost estimate of the robot’s components must be created and all revisions to the same must be recorded and explained.
**A cost estimate of the robot’s components must be created and all revisions to the estimate must be recorded and explained.
*Build Guidelines
*Build Guidelines
**The mechanism used to pick up the samples must be designed and built by the team (the use of prebuilt VEX claws is prohibited).  
**The mechanism used to pick up the samples must be designed and built (the use of prebuilt VEX claws is prohibited).  
**Projectile (catapult, slingshot) designs are not allowed.  
**Projectile (catapult, slingshot) designs are not allowed.  
*Sensor Requirement
*Sensor Requirement
Line 24: Line 24:
**The robot’s movements must be directed by an Arduino program. All revisions to the Arduino program must be recorded and explained.
**The robot’s movements must be directed by an Arduino program. All revisions to the Arduino program must be recorded and explained.
*Autonomous Navigation
*Autonomous Navigation
**The robot must be fully autonomous, and therefore cannot be touched by any person during testing. The Arduino program may not be altered or switched during any part of the mission.
**The robot must be fully autonomous, and cannot be touched during testing. The Arduino program may not be altered or switched during any part of the mission.
 
<!--Your team must build a model of your design using the materials provided. Your team must also create an Arduino program that will direct the robot’s movements. A cost estimate of the robot’s components and labor costs must be provided. All revision to the original design must be recorded and explained. This includes technical design drawings as well as cost estimates. All revisions to the Arduino program must be recorded and explained.
 
The LAZ robot must be able to move autonomously over the course, pick up the three different samples, and transport them to their designated area. The mechanism used to pick up the samples must be designed and built by the team (the use of prebuilt VEX claws is <b>prohibited</b>). The robot should fit within a 12 in x 12 in footprint (larger robots are allowed, but discouraged). Projectile (catapult, slingshot) designs are not allowed. These specifications must be met for final Commissioning.
 
The robot’s Arduino program may not be altered or switched during any part of the mission. Likewise, the robot must be fully autonomous, and therefore cannot be touched by any person during testing.-->


Please refer to the course syllabus for all due dates.  
Please refer to the course syllabus for all due dates.  


<i>This project reflects real life scenarios; the robot must be able to handle minor imperfections in the course.</i> <span style="color:red"><b>Please note that any attempt to physically step on the course will result in a point penalty in your final project grade due to safety precautions.</b></span>
<i>This project aims to reflect certain real-life scenarios. The robot must therefore be able to handle minor imperfections in the course.</i> <span style="color:red"><b>Please note that any attempt to physically step on the course is unsafe and will result in a point penalty in the final project grade.</b></span>


== Course Layout ==
== Course Layout ==


The LAZ course consists of three plant module pickup sites and the corresponding drop sites. The robot must pick up Plants 1 and 2 and drop them off at the corresponding location to complete the project. For extra credit, the robot can pick up Plant 3 and move it to the drop site and/or move Plants 1 and 2 back to the pickup sites. The robot must use a fully autonomous claw to pick up the plant modules and drop them off.
The LAZ course consists of three plant module pickup sites and the corresponding drop sites. The robot must pick up Plants 1 and 2 and drop them off at the corresponding location to complete the project. For extra credit, the robot can pick up Plant 3 and move it to the drop site and/or move Plants 1 and 2 back to the pickup sites. The robot must use a fully autonomous claw to pick up the plant modules and drop them off (Figure 1).


[[Image:LAZ_course.png|500px|thumb|center|Figure 1: Labeled View of the Lunar Agricultural Zone]]
[[Image:LAZ_course.png|500px|thumb|center|Figure 1: Top-view of the LAZ course]]


== Microsoft Project ==
== Microsoft Project ==


You must create a schedule to manage your time in Microsoft Project. You can learn to use Microsoft Project by accessing the [[Media:Microsoft_Project_Student_Guide.pptx|Microsoft Project Student Guide]]. This schedule must include all tasks related to the project from the start of the project to Submission. The MS Project schedule should include the following:
A project schedule must be created in Microsoft Project. Learn to use Microsoft Project by accessing the [[Media:Microsoft_Project_Student_Guide.pptx|Microsoft Project Student Guide]]. This schedule must include all tasks related to the project from the start of the project to Early or Final submission. Click [https://nyu.service-now.com/sp?id=kb_article&sysparm_article=KB0018302&sys_kb_id=b996a7281b6210906441c8c11a4bcbce&spa=1 here] to access the guide on how to transfer a file. The Microsoft Project schedule should include:
 
* Minimum of 20 tasks, excluding Milestones.
* Minimum of 20 tasks, excluding Milestones.
* Milestones should be clearly indicated on the project plan (duration of zero days).
* Milestones should be clearly indicated on the project plan (duration of zero days).
Line 57: Line 52:
== Drawings ==
== Drawings ==


All drawings and sketches should be made using the Assembly tool in <b>Fusion 360</b>. It can be downloaded for free on a personal computer using an NYU email, or accessed from any computer during Open Lab.
All drawings and sketches should be made using the Assembly tool in <b>Fusion 360</b>. It can be downloaded for free on a personal computer using an NYU email or accessed from any computer during Open Lab.


Using Fusion 360, create four drawings of the robot: front, top, most detailed side, and a drawing of the gear train(s). Sensors, motors, and gears must be included in each drawing. Smaller pieces such as nuts, bolts, and axles may be omitted from the drawings. If the robot does not use any gears, make sure to explicitly state that in your presentations.
Using Fusion 360, create four drawings of the robot: front, top, most detailed side, and a drawing of the gear train(s). Sensors, motors, and gears must be included in each drawing. Smaller pieces such as nuts, bolts, and axles may be omitted from the drawings. If the robot does not use any gears, make sure to explicitly state that in the presentations.


Each revision of the design must be documented and all changes must be presented during Milestone presentations.
Each revision of the design must be documented and all changes must be presented during Milestone presentations (Figure 2).




Line 67: Line 62:


== Model ==
== Model ==
You must build a scale model (1:1) of your design. The following materials will be provided:
Build a scale model (1:1) of the design. The following materials will be provided:
# VEX steel pieces
# VEX steel pieces
# Basic electronics prototyping kit (Reference VEX wiring guide)
# Basic electronics prototyping kit (Reference VEX wiring guide)
Line 73: Line 68:
# Motors
# Motors


The finished robot must not exceed a footprint of 12 in × 12 in. There is no height limitation. Additional materials can be supplied by your TA.
The finished robot must not exceed a footprint of 12" × 12". There is no height limitation, but be mindful of the risk of toppling. Additional materials can be supplied by a TA. An example of a LAZ robot model is shown in Figure 3.  


[[Image:LAZ_Model.png|450px|thumb|center|Figure 3: Example LAZ Robot Model]]
[[Image:LAZ_Model.png|450px|thumb|center|Figure 3: Example LAZ Robot Model]]
Line 81: Line 76:
Once a robot design is complete, a cost estimate must be generated that specifies the cost of all the materials and labor required for the construction of the design. Tabulate this cost information clearly in an Excel spreadsheet, using the materials cost list provided. Help in calculating the cost is available by reviewing [[how to plan the schedule and calculate costs for a project]]. The costs for the parts can be found on the [[Media:Vex_Price_Sheet.xlsx | price list for VEX parts for robot projects]].
Once a robot design is complete, a cost estimate must be generated that specifies the cost of all the materials and labor required for the construction of the design. Tabulate this cost information clearly in an Excel spreadsheet, using the materials cost list provided. Help in calculating the cost is available by reviewing [[how to plan the schedule and calculate costs for a project]]. The costs for the parts can be found on the [[Media:Vex_Price_Sheet.xlsx | price list for VEX parts for robot projects]].
The cost estimate should include the following:
The cost estimate should include the following:
* Labor cost breakdown with hours and rates
* Labor cost breakdown with hours and rates ($50.00 per person per hour)
* Consolidate low-cost pieces: axles, beams, bricks, bushings, connectors, gears, plates
* Consolidate low-cost pieces: axles, beams, bricks, bushings, connectors, gears, plates
* Consolidate electrical components: microcontroller, breadboard, wires, battery, motor shield, etc
* Consolidate electrical components: microcontroller, breadboard, wires, battery, motor shield
* Itemize high-cost pieces: sensors and motors
* Itemize high-cost pieces: sensors and motors
* No decimal places; this is an estimate after all. Round appropriately
* No decimal places; this is an estimate after all. Round appropriately
* Total cost must be shown in the bottom right corner
* Total cost must be shown in the bottom right corner of the table


<b>Note: You should only use the materials contained in the [[Media:Vex_Price_Sheet.xlsx | price list for VEX parts for robot projects]]. If you want to use other parts, <span style="color:red;">get permission from your faculty member to do so</span>, and also to determine the cost of the parts you want to use that are not in this price list.</b>
<b>Note: List only the materials from the [[Media:Vex_Price_Sheet.xlsx | price list for VEX parts for robot projects]]. To use other parts,  and to determine the cost of the additional parts that are not in this price list, <span style="color:red;">get assistance from a TA.</span></b>


== CATME ==
== CATME ==
When working on engineering team projects, peer evaluations and self-evaluations are critical for assessing how effective your contributions are to the team. In our course, your recitation professor will use evaluations at each Milestone using a software called the Comprehensive Assessment of Team Member Effectiveness (CATME). More information can be found on the [[Teamwork Expectations]] page.
When working on engineering team projects, peer evaluations and self-evaluations are critical for assessing how effective your contributions are to the project. In this course, the recitation professor will use evaluations at each Milestone using a software called the Comprehensive Assessment of Team Member Effectiveness (CATME). More information can be found on the [[Teamwork Expectations]] page.


== Engineering Notebook ==
== Engineering Notebook ==


While working on your project, you are expected to keep a record of all work done, as well as future plans and goals. In order to complete a Benchmark assessment, show your Engineering Notebook to the Open Lab TA completing your assessment. For Milestone 1, Milestone 2, Milestone 3, and Final Submission you must have it approved by your Recitation Professor and be prepared to make it available to an Open Lab TA in a Word Document (DOC or DOCX) format. A guide to writing the notebook, as well as a basic overview of its expectations and frequency at which you should log in your notebook, can be found on the [[Keeping an Engineering Notebook]] page.
All work done on the project and future plans and goals must be documented in an Engineering Notebook. To complete a Benchmark assessment, the Engineering Notebook must be presented to the Open Lab TA completing the assessment. For Milestone 1, Milestone 2, Milestone 3, and Early or Final Submission, the Engineering Notebook must be approved by the recitation professor and be prepared to make it available to an Open Lab TA in a Word Document (.doc or .docx) format. A guide to writing the notebook and a basic overview of the expectations and frequency at which the Engineering Notebook must be updated can be found on the [[Keeping an Engineering Notebook]] page.


= Milestones, Benchmarks, and Deliverables =
= Milestones, Benchmarks, and Deliverables =
As you work on your project, you will be required to present periodic reports on your progress. We call these Milestones. All the items assigned in each phase of the project are called Benchmark deliverables. These deliverables often consist of a combination of written submissions, presentations, and demonstrations. Benchmark assessments evaluate the progress of the progress.  
As work is done on the project, three Milestone presentations will report on the project's progress. All of the items assigned in each phase of the project are called Benchmark deliverables. These deliverables often consist of a combination of written submissions, presentations, and demonstrations. Benchmark assessments evaluate the progress of the project.  


== Preliminary Design Investigation ==  
== Preliminary Design Investigation ==  


The Preliminary Design investigation (PDI) is extremely important, as it lays the groundwork for your project. You will be outlining your project idea, inspiration, and goals.
The Preliminary Design investigation (PDI) is extremely important, as it lays the groundwork for the project. It outlines the project idea, inspiration, and goals.


The PDI must include:
The PDI must include:
Line 119: Line 114:
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''


Milestone 1 is a presentation of your Preliminary Design Investigation. It is important that you outline your project goals and show that your project is realizable.  
Milestone 1 is a presentation of the PDI. It is important that it outlines the project goals and shows that the project is realizable.  


Your Milestone 1 presentation must include:
The Milestone 1 presentation must include:
* Company profile
* Company profile
** Company name
** Company name
** Product name
** Product name
** Group member title(s)
** Company officer title(s)
** Mission statement
** Mission statement
* Project objective
* Project objective
** What is your project about?
** What is the project about?
** What tasks are you aiming to accomplish? (Benchmark A requirements)
** What tasks is the company aiming to accomplish? (Benchmark A requirements)
** Overall design approach to complete objective
** Overall design approach to complete objective
* Background information
* Background information
Line 136: Line 131:
* Technical design description
* Technical design description
** Preliminary conceptual drawing of robot design
** Preliminary conceptual drawing of robot design
*** Rendered and digital sketches are acceptable, CAD not required
** What components will be used and why?
** What components will be used and why?
* Cost estimate
* Cost estimate
Line 145: Line 141:
* Teamwork agreement summary
* Teamwork agreement summary
* Summary
* Summary
** Overall assessment on current state of project
** Overall assessment on the current state of the project
** Are you on schedule? Are you on budget?
** Is the project on schedule? Is it within budget?
** Next steps and future tasks
** Next steps and future tasks
<b>Look Ahead: What tasks are planned between now and Milestone 2?</b>


== Benchmark Assessment A ==
== Benchmark Assessment A ==


Benchmark assessments evaluate the progress of your project.<b>Benchmark Assessment A is due at the end of Model Shop Session II.</b> There are penalties for not completing this on time. Refer to the [[EG1004 Grading Policy]] for more information.
Benchmark assessments evaluate the progress of the project.<b>Benchmark A is due at the end of Model Shop Session II.</b> There are penalties for not completing this on time. Refer to the [[EG1004 Grading Policy]] for more information.


To pass, the design must complete all of the following:
To pass, the design must complete all of the following:
* Robot travels to Plant 1 and successfully lifts Plant 1
* Robot travels to Plant 1 and successfully lifts Plant 1
* Robot must have a fully functioning claw. For help with claw designs, refer to the [https://manual.eg.poly.edu/index.php/VEX_Lift_%26_Claw_Design_Guide VEX Lift & Claw Guide]
* Robot must have a fully functioning claw. For help with claw designs, refer to the [https://manual.eg.poly.edu/index.php/VEX_Lift_%26_Claw_Design_Guide VEX Lift & Claw Guide]
* Preliminary Design Investigation
* Initial CAD Model
* Submit an .STL and a .gcode file of the team logo or extra credit print through the 3D Printing Submission portal on the EG website
* PDI
* Submit an .STL and a .3mf (Bambu Studio Project file) of the company logo through the 3D Printing Submission portal on the EG website
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** The protolab schedule is available on the [[3D Printing and Logo Guide]]
** The ProtoLab schedule is available on the [[3D Printing and Logo Guide]]
* Updated Engineering Notebook
* Updated Engineering Notebook


Line 169: Line 163:
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''


Milestone 2 will be a project progress update. You must explain all changes and developments made thus far, particularly in regards to Benchmark A. Include whether or not you were able to complete your Benchmark A requirements, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general. Your Milestone 2 presentation must include:
Milestone 2 will be a project progress update. It must explain all changes and developments made to date, particularly in regards to Benchmark A. Include whether or not Benchmark A requirements are completed, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general.  


* Project description
The Milestone 2 presentation must include:
* Design approach
* Design changes since Milestone 1
* Mission statement
* Technical design description:
** CAD drawings: top, front, most detailed side, isometric, gear train
** Flowchart of Code
** Circuit Diagram
* Cost estimate (previous and current). What changes were made?
* Microsoft Project schedule (previous and current). What changes were made?
** Click [https://nyu.service-now.com/sp?id=kb_article&sysparm_article=KB0018302&sys_kb_id=b996a7281b6210906441c8c11a4bcbce&spa=1 here] to access the guide on how to transfer a file
* Progress update: current state of the project (time, budget, etc.)


 
* Company profile
<b>Look Ahead: What tasks are planned between now and Milestone 3?</b>
** Company name
** Product name
** Company officer title(s)
** Mission statement
* Project objective
** What is the project about?
** What tasks is the company aiming to accomplish? (Benchmark A/Benchmark B requirements)
** Overall design approach to complete objective
* Background information
** Why is the project happening?
** What does the audience need to know?
* Technical design description
** Explanation of design changes, if any
** CAD drawings: top, front, most detailed side, isometric, and gear train view
** Circuit and schematic diagram(s)
** Relevant pictures
** Flowchart of code
* Cost estimate (previous and current costs)
** Major components of design listed
** Miscellaneous category listed
** Projected labor listed
** What changes were made, if any?
* Microsoft Project schedule (previous and current)
** What changes were made, if any?
** Click [https://nyu.service-now.com/sp?id=kb_article&sysparm_article=KB0018302&sys_kb_id=b996a7281b6210906441c8c11a4bcbce&spa=1| here] to access the guide on how to transfer a file
* Summary
** Overall assessment on current state of project
** Is the project on schedule? Is it on budget?
** Next steps and future tasks


== Benchmark Assessment B ==
== Benchmark Assessment B ==


<b>Benchmark Assessment B is due at the end of Model Shop Session III.</b> There are penalties for not completing on time. Refer to the [[EG1004 Grading Policy]] for more information.
<b>Benchmark B is due at the end of Model Shop Session III.</b> There are penalties for not completing on time. Refer to the [[EG1004 Grading Policy]] for more information.


To pass, the design must complete all of the following:
To pass, the design must complete all of the following:
* After retrieving Plant 1 in Benchmark A, the robot delivers Plant 1 to the Plant 1 Drop Site and travels to Plant 2
* After retrieving Plant 1 in Benchmark A, the robot delivers Plant 1 to the Plant 1 Drop Site and travels to Plant 2
* The robot must touch Plant 2  
* The robot must touch Plant 2  
* Have an .STL and a .gcode file of the team logo or extra credit print approved through the 3D Printing Submission portal on the EG website
* Updated CAD model
* Have an .STL and a .3mf (Bambu Studio Project file) of the company logo approved by a ProtoLab TA through the 3D Printing Submission portal on the EG website. Students must physically go to the ProtoLab before the Modelshop Session 3 to get the logo approved. Logos cannot be approved during Modelshop sessions.
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** The protolab schedule is available on the [[3D Printing and Logo Guide]]
** The ProtoLab schedule is available on the [[3D Printing and Logo Guide]]
* Updated Engineering Notebook
* Updated Engineering Notebook


Line 203: Line 215:
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''
'''<span style="color: red;">See [[Media:Eg_milestones.pptx|How To Give a Milestone Presentation]] for the format of a Milestone presentation.</span>'''


Milestone 3 will be the last project progress update. You must explain all changes and developments made thus far, particularly in regards to Benchmark B. Include whether or not you were able to complete your Benchmark B requirements, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general. Your Milestone 3 presentation must include:
Milestone 3 will be the last project progress update. It must explain all changes and developments made to date, particularly in regards to Benchmark B. Include whether or not Benchmark B requirements are completed, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general.  
* Project description
* Design approach
* Design changes since Milestone 2
* Mission statement
* Technical design description:
** CAD drawings: top, front, most detailed side, isometric, gear train
** Flowchart of Code
** Circuit and Schematic Diagrams
* Cost estimate (previous and current). What changes were made?
* Microsoft Project schedule (previous and current). What changes were made?
** Click [https://nyu.service-now.com/sp?id=kb_article&sysparm_article=KB0018302&sys_kb_id=b996a7281b6210906441c8c11a4bcbce&spa=1 here] to access the guide on how to transfer a file
* Progress update: current state of the project (time, budget, etc.)


The Milestone 3 presentation must include:


<b>Look ahead: What tasks are planned between now and the completion of the project?</b>
* Company profile
** Company name
** Product name
** Company officer title(s)
** Mission statement
* Project objective
** What is the project about?
** What tasks is the company aiming to accomplish? (Benchmark A/Benchmark B requirements)
** Overall design approach to complete objective
* Background information
** Why is the project happening?
** What does the audience need to know?
* Technical design description
** Explanation of design changes, if any
** CAD drawings: top, front, most detailed side, isometric, and gear train view
** Circuit and schematic diagram(s)
** Relevant pictures
** Flowchart of code
* Cost estimate (previous and current costs)
** Major components of design listed
** Miscellaneous category listed
** Projected labor listed
** What changes were made, if any?
* Microsoft Project schedule (previous and current)
** What changes were made, if any?
** Click [https://nyu.service-now.com/sp?id=kb_article&sysparm_article=KB0018302&sys_kb_id=b996a7281b6210906441c8c11a4bcbce&spa=1| here] to access the guide on how to transfer a file
* Summary
** Overall assessment on current state of project
** Is the project on schedule? Is it on budget?
** Next steps and future tasks


= Commissioning =
= Commissioning =
Line 227: Line 257:
* After traveling to Plant 2, the robot delivers Plant 2 to the Plant 2 drop site
* After traveling to Plant 2, the robot delivers Plant 2 to the Plant 2 drop site
* Robot meets all specifications
* Robot meets all specifications
* Have an .STL file of the team logo or extra credit print printed through the 3D Printing Submission portal on the EG website
* Finalized CAD model
* Have an .STL file of the company logo printed through the 3D Printing Submission portal on the EG website
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** <b>The [[3D Printing and Logo Guide]] contains information on the 3D printing requirements and guidelines</b>
** The protolab schedule is available on the [[3D Printing and Logo Guide]]
** The ProtoLab schedule is available on the [[3D Printing and Logo Guide]]
* All 3D prints must be approved by a Protolab TA
* All 3D prints must be approved by a ProtoLab TA
* Updated Engineering Notebook
* Updated Engineering Notebook


Line 237: Line 268:
== Extra Credit ==
== Extra Credit ==


LAZ Groups have multiple opportunities for extra credit. These include:
LAZ designs have multiple opportunities for extra credit. These include:
<!--* After completing all commissioning requirements, bring all the samples back to their original starting position.-->
 
* Retrieving Plant 3 and delivering it to the Plant 3 Drop Site.
* Retrieving Plant 3 and delivering it to the Plant 3 Drop Site.
* Completing Benchmark A or Benchmark B in reverse
* Completing Benchmark A or Benchmark B in reverse
** Robot retrieves Plant 1 from Drop Site and returns it to its original position
** Robot retrieves Plant 1 from Drop Site and returns it to its original position
** Robot retrieves Plant 2 from Drop Site and returns it to its original position
** Robot retrieves Plant 2 from Drop Site and returns it to its original position
*Implementing an additional sensor
 
* Completing Benchmark A, Benchmark B, or Submission early, or
Additional extra credit opportunities are as follows:
* Completing your respective SLDP's 3D printing extra credit task as described in the [[3D Printing and Logo Guide]].
* Completing Early Submission  


Refer to the [[EG1004 Grading Policy]] for exact point values. Creativity and innovation are always rewarded. Original designs will receive extra credit.
Refer to the [[EG1004 Grading Policy]] for exact point values. Creativity and innovation are always rewarded. Original designs will receive extra credit.
Line 251: Line 282:
= Final Design Report =
= Final Design Report =


The Final Design Report (FDR) provides a comprehensive overview of your project process and developments from initial brainstorm to finished proof of concept. All project expectations and outcomes must be clearly detailed in the document. This report will also provide you with documentation experience useful for completing your Senior Design final report and other projects.
The Final Design Report (FDR) provides a comprehensive overview of your project process and developments from initial brainstorm to finished prototype. All project expectations and outcomes must be clearly detailed in the document. This report will also provide documentation experience useful for completing a Senior Design final report and other projects.


The Final Design Report must include the following documentation:
The FDR must include the following documentation:
* CAD drawings
* CAD drawings
* Wiring Diagrams
* Wiring diagrams
* Commented code
* Project schedule
* Project schedule
* Cost estimate
* Cost estimate


Use this [[Media:LAZ_Final_Design_Report.docx|Final Design Report]] template with the following outline:
The FDR uses different section headers and content than those in the lab reports, but all FDRs must follow the [[Media:EG_1004_Writing_Style_Guide.pdf| EG1004 Writing Style Guide]]. Use this [[Media:MRR_Final_Design_Report.docx|FDR]] template with the following outline:
 
* Introduction
* Introduction
** Purpose of Project
** Purpose of Project
Line 288: Line 319:
= Final Presentation =
= Final Presentation =


The final presentation will be a technical briefing, similar to the milestones, but also serves as a sales presentation explaining why your company should be selected instead of the competition. Please include the following:
The Final Presentation will be a technical briefing, similar to the Milestones, but also serves as a sales presentation explaining why the company should be selected instead of the competition.  
 
The Final Presentation must include:
 
* Company profile
** Company name
** Company officer profile(s), role(s), and qualifications
** Mission statement
* Problem statement
* Problem statement
* Solution overview
** Why is the project happening?
* Company description and qualifications
** What does the audience need to know?
* CAD Drawings
* Project objective
* Flowchart of Code
** What is the purpose of your project?
* Circuit and Schematic Diagrams
** Who does the project help?
* Cost estimate
** What problem does the project solve?
* Microsoft Project schedule
* Project description
* Video demonstration
** Explanation of design changes, if any
* Why should your company be awarded this contract?
** CAD drawings: top, front, most detailed side, isometric, and gear train view
 
** Relevant pictures
** Flowchart of code
* Market and product viability
** Does the company have competitors?
** What makes the project unique?
** How does the design compare to competitors - cost, quality, features?
** Is the project versatile? 
** What is the price of the project?
* Conclusion
** Reiterating project purpose
** Highlight project features
** Future goals of the company
** Why should the company be awarded this contract?
* Video pitch
** Price of project
** Demonstration of robot run
** Embedded into Final Presentation


= Submission =
= Submission =


All SLDPs must submit online. Please visit https://eg.poly.edu/finalSLDP.php for login information and the link to the Project Submission form.
All SLDPs must be submitted online. Please visit [https://eg.poly.edu/finalSLDP.php this page] for the link to the Project Submission form and each project’s individualized login information. To submit, login to the EG1004 website using this special login information. Submitting with an NYU account or any other account will generate an error. Components may be resubmitted at any time before the deadline. Please note that submission times are based on the most recent submission.
 
Students must be logged into the account provided at https://eg.poly.edu/finalSLDP.php. Submitting with your NYU account or any other account will generate an error.


Submissions may be edited at any time before the deadline. Please note that submission times are based on the last submission. Submissions that qualify for Early Submission will lose the Early Submission Extra Credit if the submission is edited after the Early Submission deadline.
Please note the deliverables for this project are as follows. If any of the following items are omitted, there will be a penalty. Be sure to click "Submit" at the bottom of the form and allow sufficient time for uploading.


Please note the deliverables for this project are as follows. If any of the following items are omitted, you will be penalized. Be sure to click <b>SUBMIT</b> at the bottom of the form.
The following list includes deliverable items that are required:


*Submission deliverables:
*Submission deliverables:
Line 316: Line 368:
** Final Circuit Diagrams
** Final Circuit Diagrams
** Initial sketch
** Initial sketch
** All the drawings of your design (initial through final)
** All the drawings of the design (initial through final)
** Video
** Video
** Final MS Project Schedule
** Final Microsoft Project Schedule
** Final cost estimate
** Final cost estimate
** Resume(s) (No fictitious resumes will be accepted.)
** Resume(s) (No fictitious resumes will be accepted.)
Line 326: Line 378:
== Early Submission ==
== Early Submission ==


If you submit your project one week early, you are eligible for a bonus that will be added to your final semester-long project grade. You must submit all deliverables one week before the submission deadline (see syllabus for exact date). The deliverables received early are the ones you will use in your presentation. No adjustments to the deliverables submitted will be accepted.
If the project is submitted one academic week early (before the end of the lab period the week before the Final Submission deadline), the project is eligible for a bonus that will be added to the final SLDP grade. All deliverables must be submitted one academic week before the submission deadline (see syllabus for the exact date). The deliverables received early are the ones that will be used in the Final Presentation. No changes to the submitted deliverables will be accepted.
   
   
== Late Submission ==
== Late Submission ==


Late submission is not allowed. If you do not commission or partial commission by the deadline set forth in the syllabus, you will not be allowed to submit and will receive a 0 for the project grade. In order to receive partial commissioning, two TAs must analyze the project and determine its level of completeness in terms of commissioning requirements. Please refer to the [[EG1004 Grading Policy]] for more information.
Late submission is not allowed. If a project does not Commission or receive Partial Commission by the deadline set forth in the syllabus, the project will not be allowed to submit and will receive a 0 for the project grade. To receive Partial Commissioning, two TAs must evaluate the project and determine its degree of completion according to the Commissioning requirements and the project will be given a grade accordingly. Please refer to the [[EG1004 Grading Policy]] for more information.


= Frequently Asked Questions =
= Frequently Asked Questions =
<b>Q: Can we step onto the course as it is hard to reach the middle due to its size?</b>
<b>Q: Is stepping on the course allowed as it is difficult to retrieve a robot from the middle of the course due to its size?</b>


A: No. If needed, you can have a TA assist you.
A: No. If needed, ask a TA for assistance.


<b>Q: Can we bump the course if the robot gets stuck?</b>
<b>Q: Can the course be bumped if the robot gets stuck?</b>


A: No. You can't bump the Moon, so bumping the course is not an option.
A: No. It is not possible to bump the Moon, so bumping the course is not an option.


<b>Q: All the VEX parts are really big. Is there a size constraint?</b>
<b>Q: All the VEX parts are really big. Is there a size constraint?</b>


A: There is a soft size-limitation of 12 in x 12 in. If you slightly exceed this constraint, it is ok, but you will have difficulties due to the sizing of the course.
A: There is a size limitation of a 12 in x 12 in footprint. Exceeding this constraint is okay, but it may create difficulties when the robot is navigating the course.


<b>Q: What is a common mistake to avoid?</b>
<b>Q: What is a common mistake to avoid?</b>
   
   
A: Starting your project late. Note that Benchmark A requires you to have a robot with a functioning claw mechanism and building VEX robots can be tedious.  
A: Starting the project late. Note that Benchmark A requires a robot with a functioning claw mechanism and building VEX robots can be tedious.  


<b>Q: How should I get started with building the LAZ Claw?</b>
<b>Q: What is the best way to build the LAZ Claw?</b>
   
   
A: For help with claw designs, refer to the [[VEX Lift & Claw Design Guide]].  
A: For help with claw designs, refer to the [[VEX Lift & Claw Design Guide]].  
   
   
<b>Q: What materials can I use for the VEX Claw?</b>
<b>Q: What materials can be used use for the VEX Claw?</b>
   
   
A: EG’s LAZ inventory includes Linear Motion Kits, Sprockets & Chains, and Tank Treads. These materials have limited availability, so first come, first serve.  
A: EG’s LAZ inventory includes Linear Motion Kits, Sprockets & Chains, and Tank Treads. These materials have limited availability, so first come, first serve.  
   
   
<b>Q: How can I make my VEX robot more consistent?</b>  
<b>Q: How can the VEX robot's performance be more consistent?</b>  
   
   
A: Sensors are very helpful when it comes to consistency. Additionally, you may use the walls on LAZ to align your robot. Just make sure you’re not ramming your robot into the course which can damage it.   
A: Sensors are very helpful when it comes to consistency. Additionally, use the walls on LAZ course to align the robot. Just make sure the robot is not ramming into the course, which can damage it.   
   
   
<b>Q: My robot is having a hard time making turns on the course, how can I fix that?</b>  
<b>Q: The robot is having a hard time making turns on the course, how can that be fixed?</b>  
   
   
A: Each LAZ group is allowed to use two omni-wheels, which help robots make turns more easily. Adding clear tape onto the regular VEX wheels also helps.
A: Each LAZ design is allowed to use two omni-wheels, which help robots make turns more easily. Adding clear tape onto the regular VEX wheels also helps.

Latest revision as of 11:08, 4 March 2024

Request for Proposal: Lunar Agricultural Zone (LAZ)



Introduction and Overview

Humanity faces the problem of feeding its growing population. Currently, half of the Earth’s habitable land (51 million km2) is used for agriculture, leaving little for much else. To combat this, the National Aeronautics and Space Administration (NASA) has turned to lunar agriculture. With a surface area of over 37 million km2, the moon has the potential to produce over 70% of the Earth’s current food supply. Due to the slow period of rotation, stationary crops on the moon will be exposed to 27.3 days of continuous sunlight and then darkness. To have greater control over the sunlight exposure of crops on the moon, NASA has issued a request for a proposal for an autonomous rover that is capable of traversing the Lunar Agricultural Zone (LAZ), the newest solution to world hunger. This rover would traverse the unsmooth terrains of the moon, locate various crops, and determine if they should be moved depending on the levels of light exposure detected. By keeping rigorous control of the light exposure of the crops, NASA hopes to create an environment capable of sustaining plant life on the moon.

The objective of this mission is to locate and collect all plants in the LAZ that are overexposed to sunlight. To complete the tasks, a gyro, touch, or ultrasonic sensor can be used to increase the accuracy of the rover's movement. After the overexposed plants are obtained, they should be transported to an area of less exposure.

Specifications

Design a robot using Fusion 360 as the primary design tool. The robot must meet the following specifications:

  • Size & Material Constraints
    • The robot should ideally fit within a 12" x 12" footprint. Larger robots are allowed but discouraged.
    • A cost estimate of the robot’s components must be created and all revisions to the estimate must be recorded and explained.
  • Build Guidelines
    • The mechanism used to pick up the samples must be designed and built (the use of prebuilt VEX claws is prohibited).
    • Projectile (catapult, slingshot) designs are not allowed.
  • Sensor Requirement
    • The design must incorporate a sensor of choice. This could be a gyro sensor, ultrasonic sensor, or touch sensor.
  • Microcontroller Requirement
    • The robot’s movements must be directed by an Arduino program. All revisions to the Arduino program must be recorded and explained.
  • Autonomous Navigation
    • The robot must be fully autonomous, and cannot be touched during testing. The Arduino program may not be altered or switched during any part of the mission.

Please refer to the course syllabus for all due dates.

This project aims to reflect certain real-life scenarios. The robot must therefore be able to handle minor imperfections in the course. Please note that any attempt to physically step on the course is unsafe and will result in a point penalty in the final project grade.

Course Layout

The LAZ course consists of three plant module pickup sites and the corresponding drop sites. The robot must pick up Plants 1 and 2 and drop them off at the corresponding location to complete the project. For extra credit, the robot can pick up Plant 3 and move it to the drop site and/or move Plants 1 and 2 back to the pickup sites. The robot must use a fully autonomous claw to pick up the plant modules and drop them off (Figure 1).

Figure 1: Top-view of the LAZ course

Microsoft Project

A project schedule must be created in Microsoft Project. Learn to use Microsoft Project by accessing the Microsoft Project Student Guide. This schedule must include all tasks related to the project from the start of the project to Early or Final submission. Click here to access the guide on how to transfer a file. The Microsoft Project schedule should include:

  • Minimum of 20 tasks, excluding Milestones.
  • Milestones should be clearly indicated on the project plan (duration of zero days).
  • Each task must include the person responsible for completing the task (resource names).
  • Use the "Copy Picture" function to include the project plan in the presentations. Do not take a screenshot.
  • Gantt chart must be displayed alongside the tasks list (fit onto one slide).
  • Gantt chart must clearly show a progress line.
  • Clearly state during the presentation whether the project is on-time, behind schedule, or ahead of schedule.

For help in planning the project, review the manual page How to plan the schedule and calculate costs for a project.

Drawings

All drawings and sketches should be made using the Assembly tool in Fusion 360. It can be downloaded for free on a personal computer using an NYU email or accessed from any computer during Open Lab.

Using Fusion 360, create four drawings of the robot: front, top, most detailed side, and a drawing of the gear train(s). Sensors, motors, and gears must be included in each drawing. Smaller pieces such as nuts, bolts, and axles may be omitted from the drawings. If the robot does not use any gears, make sure to explicitly state that in the presentations.

Each revision of the design must be documented and all changes must be presented during Milestone presentations (Figure 2).


Figure 2: Example Drawing of LAZ robot

Model

Build a scale model (1:1) of the design. The following materials will be provided:

  1. VEX steel pieces
  2. Basic electronics prototyping kit (Reference VEX wiring guide)
  3. Sensors
  4. Motors

The finished robot must not exceed a footprint of 12" × 12". There is no height limitation, but be mindful of the risk of toppling. Additional materials can be supplied by a TA. An example of a LAZ robot model is shown in Figure 3.

Figure 3: Example LAZ Robot Model

Cost Estimate

Once a robot design is complete, a cost estimate must be generated that specifies the cost of all the materials and labor required for the construction of the design. Tabulate this cost information clearly in an Excel spreadsheet, using the materials cost list provided. Help in calculating the cost is available by reviewing how to plan the schedule and calculate costs for a project. The costs for the parts can be found on the price list for VEX parts for robot projects. The cost estimate should include the following:

  • Labor cost breakdown with hours and rates ($50.00 per person per hour)
  • Consolidate low-cost pieces: axles, beams, bricks, bushings, connectors, gears, plates
  • Consolidate electrical components: microcontroller, breadboard, wires, battery, motor shield
  • Itemize high-cost pieces: sensors and motors
  • No decimal places; this is an estimate after all. Round appropriately
  • Total cost must be shown in the bottom right corner of the table

Note: List only the materials from the price list for VEX parts for robot projects. To use other parts, and to determine the cost of the additional parts that are not in this price list, get assistance from a TA.

CATME

When working on engineering team projects, peer evaluations and self-evaluations are critical for assessing how effective your contributions are to the project. In this course, the recitation professor will use evaluations at each Milestone using a software called the Comprehensive Assessment of Team Member Effectiveness (CATME). More information can be found on the Teamwork Expectations page.

Engineering Notebook

All work done on the project and future plans and goals must be documented in an Engineering Notebook. To complete a Benchmark assessment, the Engineering Notebook must be presented to the Open Lab TA completing the assessment. For Milestone 1, Milestone 2, Milestone 3, and Early or Final Submission, the Engineering Notebook must be approved by the recitation professor and be prepared to make it available to an Open Lab TA in a Word Document (.doc or .docx) format. A guide to writing the notebook and a basic overview of the expectations and frequency at which the Engineering Notebook must be updated can be found on the Keeping an Engineering Notebook page.

Milestones, Benchmarks, and Deliverables

As work is done on the project, three Milestone presentations will report on the project's progress. All of the items assigned in each phase of the project are called Benchmark deliverables. These deliverables often consist of a combination of written submissions, presentations, and demonstrations. Benchmark assessments evaluate the progress of the project.

Preliminary Design Investigation

The Preliminary Design investigation (PDI) is extremely important, as it lays the groundwork for the project. It outlines the project idea, inspiration, and goals.

The PDI must include:

  • Cover Page
  • Project Overview
  • Goals & Objectives
  • Design & Approach
  • Cost Estimate
  • Project Schedule
  • Relevant Pictures

An example PDI template can be found here. The PDI is due by Benchmark A. Do not forget to include the items listed above. Use this link to access the VEX PDI Rubric.

Milestone 1

See How To Give a Milestone Presentation for the format of a Milestone presentation.

Milestone 1 is a presentation of the PDI. It is important that it outlines the project goals and shows that the project is realizable.

The Milestone 1 presentation must include:

  • Company profile
    • Company name
    • Product name
    • Company officer title(s)
    • Mission statement
  • Project objective
    • What is the project about?
    • What tasks is the company aiming to accomplish? (Benchmark A requirements)
    • Overall design approach to complete objective
  • Background information
    • Why is the project happening?
    • What does the audience need to know?
  • Technical design description
    • Preliminary conceptual drawing of robot design
      • Rendered and digital sketches are acceptable, CAD not required
    • What components will be used and why?
  • Cost estimate
    • Major components of design listed
    • Miscellaneous category listed
    • Projected labor listed
  • Microsoft Project schedule
    • Click here to access the guide on how to transfer a file
  • Teamwork agreement summary
  • Summary
    • Overall assessment on the current state of the project
    • Is the project on schedule? Is it within budget?
    • Next steps and future tasks

Benchmark Assessment A

Benchmark assessments evaluate the progress of the project.Benchmark A is due at the end of Model Shop Session II. There are penalties for not completing this on time. Refer to the EG1004 Grading Policy for more information.

To pass, the design must complete all of the following:

  • Robot travels to Plant 1 and successfully lifts Plant 1
  • Robot must have a fully functioning claw. For help with claw designs, refer to the VEX Lift & Claw Guide
  • Initial CAD Model
  • PDI
  • Submit an .STL and a .3mf (Bambu Studio Project file) of the company logo through the 3D Printing Submission portal on the EG website
  • Updated Engineering Notebook

Milestone 2

See How To Give a Milestone Presentation for the format of a Milestone presentation.

Milestone 2 will be a project progress update. It must explain all changes and developments made to date, particularly in regards to Benchmark A. Include whether or not Benchmark A requirements are completed, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general.

The Milestone 2 presentation must include:

  • Company profile
    • Company name
    • Product name
    • Company officer title(s)
    • Mission statement
  • Project objective
    • What is the project about?
    • What tasks is the company aiming to accomplish? (Benchmark A/Benchmark B requirements)
    • Overall design approach to complete objective
  • Background information
    • Why is the project happening?
    • What does the audience need to know?
  • Technical design description
    • Explanation of design changes, if any
    • CAD drawings: top, front, most detailed side, isometric, and gear train view
    • Circuit and schematic diagram(s)
    • Relevant pictures
    • Flowchart of code
  • Cost estimate (previous and current costs)
    • Major components of design listed
    • Miscellaneous category listed
    • Projected labor listed
    • What changes were made, if any?
  • Microsoft Project schedule (previous and current)
    • What changes were made, if any?
    • Click here to access the guide on how to transfer a file
  • Summary
    • Overall assessment on current state of project
    • Is the project on schedule? Is it on budget?
    • Next steps and future tasks

Benchmark Assessment B

Benchmark B is due at the end of Model Shop Session III. There are penalties for not completing on time. Refer to the EG1004 Grading Policy for more information.

To pass, the design must complete all of the following:

  • After retrieving Plant 1 in Benchmark A, the robot delivers Plant 1 to the Plant 1 Drop Site and travels to Plant 2
  • The robot must touch Plant 2
  • Updated CAD model
  • Have an .STL and a .3mf (Bambu Studio Project file) of the company logo approved by a ProtoLab TA through the 3D Printing Submission portal on the EG website. Students must physically go to the ProtoLab before the Modelshop Session 3 to get the logo approved. Logos cannot be approved during Modelshop sessions.
  • Updated Engineering Notebook

Milestone 3

See How To Give a Milestone Presentation for the format of a Milestone presentation.

Milestone 3 will be the last project progress update. It must explain all changes and developments made to date, particularly in regards to Benchmark B. Include whether or not Benchmark B requirements are completed, and if not, explain why. Also, highlight any changes you plan on making to your design or project, in general.

The Milestone 3 presentation must include:

  • Company profile
    • Company name
    • Product name
    • Company officer title(s)
    • Mission statement
  • Project objective
    • What is the project about?
    • What tasks is the company aiming to accomplish? (Benchmark A/Benchmark B requirements)
    • Overall design approach to complete objective
  • Background information
    • Why is the project happening?
    • What does the audience need to know?
  • Technical design description
    • Explanation of design changes, if any
    • CAD drawings: top, front, most detailed side, isometric, and gear train view
    • Circuit and schematic diagram(s)
    • Relevant pictures
    • Flowchart of code
  • Cost estimate (previous and current costs)
    • Major components of design listed
    • Miscellaneous category listed
    • Projected labor listed
    • What changes were made, if any?
  • Microsoft Project schedule (previous and current)
    • What changes were made, if any?
    • Click here to access the guide on how to transfer a file
  • Summary
    • Overall assessment on current state of project
    • Is the project on schedule? Is it on budget?
    • Next steps and future tasks

Commissioning

Projects must be commissioned before Submission. Refer to the syllabus for Submission deadlines. There are penalties for not completing this on time. Refer to the EG1004 Grading Policy for more information.

To pass, the design must complete all of the following:

  • Complete tasks for Benchmark A and Benchmark B
  • After traveling to Plant 2, the robot delivers Plant 2 to the Plant 2 drop site
  • Robot meets all specifications
  • Finalized CAD model
  • Have an .STL file of the company logo printed through the 3D Printing Submission portal on the EG website
  • All 3D prints must be approved by a ProtoLab TA
  • Updated Engineering Notebook

The robot must complete the required tasks in a single run in order to obtain full credit for commissioning.

Extra Credit

LAZ designs have multiple opportunities for extra credit. These include:

  • Retrieving Plant 3 and delivering it to the Plant 3 Drop Site.
  • Completing Benchmark A or Benchmark B in reverse
    • Robot retrieves Plant 1 from Drop Site and returns it to its original position
    • Robot retrieves Plant 2 from Drop Site and returns it to its original position

Additional extra credit opportunities are as follows:

  • Completing Early Submission

Refer to the EG1004 Grading Policy for exact point values. Creativity and innovation are always rewarded. Original designs will receive extra credit.

Final Design Report

The Final Design Report (FDR) provides a comprehensive overview of your project process and developments from initial brainstorm to finished prototype. All project expectations and outcomes must be clearly detailed in the document. This report will also provide documentation experience useful for completing a Senior Design final report and other projects.

The FDR must include the following documentation:

  • CAD drawings
  • Wiring diagrams
  • Project schedule
  • Cost estimate

The FDR uses different section headers and content than those in the lab reports, but all FDRs must follow the EG1004 Writing Style Guide. Use this FDR template with the following outline:

  • Introduction
    • Purpose of Project
    • Background
  • Requirements
    • Physical Components
    • Software Components
  • Procedures
    • Physical Construction
    • Software Setup
    • Software Troubleshooting
  • Milestone and Final Product Requirements
    • Benchmark A Requirements
    • Benchmark B Requirements
    • Final Submission Requirements
    • Human Resources and Training (e.g. TA expertise utilized, etc.)
  • Results
    • Benchmark A Results
    • Benchmark B Results
    • Difficulties Experienced
  • Conclusion
    • Results of Project
    • Future Improvements

The FDR is due at the time of submission.

Final Presentation

The Final Presentation will be a technical briefing, similar to the Milestones, but also serves as a sales presentation explaining why the company should be selected instead of the competition.

The Final Presentation must include:

  • Company profile
    • Company name
    • Company officer profile(s), role(s), and qualifications
    • Mission statement
  • Problem statement
    • Why is the project happening?
    • What does the audience need to know?
  • Project objective
    • What is the purpose of your project?
    • Who does the project help?
    • What problem does the project solve?
  • Project description
    • Explanation of design changes, if any
    • CAD drawings: top, front, most detailed side, isometric, and gear train view
    • Relevant pictures
    • Flowchart of code
  • Market and product viability
    • Does the company have competitors?
    • What makes the project unique?
    • How does the design compare to competitors - cost, quality, features?
    • Is the project versatile?
    • What is the price of the project?
  • Conclusion
    • Reiterating project purpose
    • Highlight project features
    • Future goals of the company
    • Why should the company be awarded this contract?
  • Video pitch
    • Price of project
    • Demonstration of robot run
    • Embedded into Final Presentation

Submission

All SLDPs must be submitted online. Please visit this page for the link to the Project Submission form and each project’s individualized login information. To submit, login to the EG1004 website using this special login information. Submitting with an NYU account or any other account will generate an error. Components may be resubmitted at any time before the deadline. Please note that submission times are based on the most recent submission.

Please note the deliverables for this project are as follows. If any of the following items are omitted, there will be a penalty. Be sure to click "Submit" at the bottom of the form and allow sufficient time for uploading.

The following list includes deliverable items that are required:

  • Submission deliverables:
    • Final presentation
    • Final Arduino program
    • Final Circuit Diagrams
    • Initial sketch
    • All the drawings of the design (initial through final)
    • Video
    • Final Microsoft Project Schedule
    • Final cost estimate
    • Resume(s) (No fictitious resumes will be accepted.)
    • Final Engineering Notebook
    • Final Design Report

Early Submission

If the project is submitted one academic week early (before the end of the lab period the week before the Final Submission deadline), the project is eligible for a bonus that will be added to the final SLDP grade. All deliverables must be submitted one academic week before the submission deadline (see syllabus for the exact date). The deliverables received early are the ones that will be used in the Final Presentation. No changes to the submitted deliverables will be accepted.

Late Submission

Late submission is not allowed. If a project does not Commission or receive Partial Commission by the deadline set forth in the syllabus, the project will not be allowed to submit and will receive a 0 for the project grade. To receive Partial Commissioning, two TAs must evaluate the project and determine its degree of completion according to the Commissioning requirements and the project will be given a grade accordingly. Please refer to the EG1004 Grading Policy for more information.

Frequently Asked Questions

Q: Is stepping on the course allowed as it is difficult to retrieve a robot from the middle of the course due to its size?

A: No. If needed, ask a TA for assistance.

Q: Can the course be bumped if the robot gets stuck?

A: No. It is not possible to bump the Moon, so bumping the course is not an option.

Q: All the VEX parts are really big. Is there a size constraint?

A: There is a size limitation of a 12 in x 12 in footprint. Exceeding this constraint is okay, but it may create difficulties when the robot is navigating the course.

Q: What is a common mistake to avoid?

A: Starting the project late. Note that Benchmark A requires a robot with a functioning claw mechanism and building VEX robots can be tedious.

Q: What is the best way to build the LAZ Claw?

A: For help with claw designs, refer to the VEX Lift & Claw Design Guide.

Q: What materials can be used use for the VEX Claw?

A: EG’s LAZ inventory includes Linear Motion Kits, Sprockets & Chains, and Tank Treads. These materials have limited availability, so first come, first serve.

Q: How can the VEX robot's performance be more consistent?

A: Sensors are very helpful when it comes to consistency. Additionally, use the walls on LAZ course to align the robot. Just make sure the robot is not ramming into the course, which can damage it.

Q: The robot is having a hard time making turns on the course, how can that be fixed?

A: Each LAZ design is allowed to use two omni-wheels, which help robots make turns more easily. Adding clear tape onto the regular VEX wheels also helps.

Retrieved from "https://manual.eg.poly.edu/index.php?title=Lunar_Agricultural_Zone_(LAZ)&oldid=15083"