| Project Summary | Project Information |
|---|---|
|
For an updated project description, click on the following link for the Project Readiness Package. In this project, the problem being addressed is using alternative forms of communication to interact with robots. The goal is to create a robot that can process user-gestures (e.g., sign language) to perform tasks that the user may not be able to complete on their own. For this project, the robot will be designed to understand a gesture that indicates to the robot to pour a glass of water. The short term goal of this project is to be able to detect one specific gesture and have to robot do one simple task: pouring a cup of water. In the long-term, this project could support programs such as those that advance medical care and quality of life for those in assisted living. The main purpose of this project is to create a robot that will pour a glass of water after the user does a certain gesture. The robot will stand idly by at its docking station until it is activated. Upon activation, the robot will recognize a specific gesture that will indicate to it to perform its task of pouring water. The robot will function by using path mapping with object collision sensors and image recognition software. When the robot becomes active, it will immediately scope the area for the cup. After the robot has detected this object, it then waits for a specific gesture before performing the task. The robot will then perform environmental mapping using both image processing and collision sensors to create the best path towards the user. This path will be stored in memory so that it can take the same path back to the dock. When the robot reaches its destination, it will then pour the correct amount of water based on water level sensors that the robot has. After this task has been completed the robot will then return back to its docking station. Part of the project is to design and create the robot. Because the robot is not on hand it does not know how to execute the pouring function. Because the robot is going to be made from scratch the budget can be a little tight. Additional funds from grants or other companies will be sought out for this project. There are no requirements for the software platform of the robot. Final software and mechanisms can be flexible after engineering team has decided if the project is plausible within the time frame. 
|
|
Team Members
put team photo here
| Member | Role | Contact |
|---|---|---|
| Kaleb Kang | Project Manager | mailto:kmk4834@g.rit.edu |
| William Reid | Biomedical Engineer | mailto:wjr3714@g.rit.edu |
| Yogi Kanakamedala | Computer Engineer | mailto:yk2035@rit.edu |
| Nathaniel Wilcox | Electrical Engineer | mailto:nxw4660@g.rit.edu |
| Soren Suver | Electrical Engineer | mailto:sas3806@rit.edu |
| Michael Johnson | Mechanical Engineer | mailto:mxj5897@rit.edu |
| Elise King | Mechanical Engineer | mailto:ejk8928@rit.edu |
| James Oakes | Mechanical Engineer | mailto:jho1101@rit.edu |
Information
Content Guidelines: Use these links below to guide you in populating your website. A few points to consider:
- Be aware of any information that you or your sponsor might not want publicly available: confidential information, personal phone numbers, photos, etc. You can use the private directory for this information, and it will be available only to those users with Guest access to your site. Remember that once you post something online, it's nearly impossible to remove it entirely!
- Do not post any files on your site that are not yours, unless you are certain that they are in the public domain or you have received permission to post them. Examples of files that you should avoid posting are copies of published papers, standards documents, textbook chapters/excerpts, or copyrighted images. If you have received a .pdf of a paper through Interlibrary Loan, or purchased an ASTM or ISO standard, you may post it in the private directory, where only your team and guide will have access to it.
- If you are including contact information for people that would otherwise not be publicly available, make sure you have their permission. For example, your faculty advisor's email address and office phone number are already publicly available on the KGCOE website, and is fine to post. However, if he or she has provided a cell phone number to the team, that is most likely not public information and should not be posted without explicit permission.
- Comment out this text once you've read it.
Work Breakdown: By Phase
| MSD I & II | MSD I | MSD II |
|---|---|---|
|
Integrated System Build & Test Customer Handoff & Final Project Documentation (Verification & Validation) |
Work Breakdown: By Topic
Use this space to link to live/final documents throughout the project. Your team should customize this as-needed, with input from your guide and customer. The example below will address most of what most teams need to capture.
| Project Management | Design Tools | Design Documentation | Implementation | Validation | Presentation & Dissemination |
|---|---|---|---|---|---|
|
PRP Requirements Schedule Cost Risk Management Problem Management Communication & Minutes |
Use Cases Benchmarking Functional Decomposition Morphological Chart Pugh Concept Selection |
BOM Mechanical Drawings Electrical Schematics Software Diagrams Facility Layout Manuals |
Mockups Test Fixtures Prototyping Test Plans |
Analysis Results Simulations Test Results |
Design Review Documents Technical Paper Poster Imagine RIT Exhibit |
Acknowledgements
- Be sure to include any relevant sponsor acknowledgement throughout your site.
- Acknowledge any other support you have received from people at RIT or elsewhere.
- Viewing the latest revision
- Node updated 2019-08-29 13:39 by sas3806