Table of Contents
The purpose of this project is for students to develop a small robotic Motor Module that will propel a robotic platform capable of payloads up to 1kg in weight. There have been past efforts to develop robotic Motor Modules and robotic Platforms, and these are outlined in the Family of Projects Overview Figure below. The ultimate goal of the development of these Robotic Platforms is to provide off-the-shelf selections of mobile Robotic Platforms for future design projects, faculty projects or student groups in need of a mobile platform. The designs of these Robotic Platforms will be fully documented and be public domain for anybody to access and build their own so that the public may focus on the design of what will be placed on the Robotic Platform instead of the platform itself.
- Project Name
- RP1 Motor Module, First Generation, Mechanical Design Focus Team
- Project Number
- Project Family
- Robotic Platform Family
- Vehicle Systems Technology
- Start Term
- End Term
- Faculty Guide
- Dr. E. Hensel, P.E. (ME)
- Faculty Consultant
- Dr. W. Walter (ME)
- Dr. D. Phillips (EE)
- Graduate Teaching Assistant
- Jason Kenyon (ME)
- Jasen Lomnick (ME)
- Primary Customer
- Dr. E. Hensel, P.E. (ME)
- Customer contact information
- RIT Mechanical Engineering Department
- Mechanical Engineering Department Head
- Email: email@example.com
- Phone: 585-475-2162
- Office: 09-2203
This outline for the posting of team created documents follows the general product development process presented in the textbook "Product Design and Development" by Ulrich and Eppinger.
Portions of the team documents have been prepared by a DPM student prior to the launch of this project. This information is intended to help get the team started with a first draft needs assessment and work breakdown structure. The team members can adapt this information as the project progresses.
Keep in mind that everything you include in this web tree is visible to the world and the general public. If you have documents that reflect work in progress, or contain data that has not been fully vetted, then it may be better to include those internal working documents in the private section of the web tree, or in the project repository proper, outside of the web tree. Note that anyone with Guest or higher memberhsip in your project can read your entire project repository. Anyone with an Editor or higher membership can makes changes to your repository. All Observer members can view, but not edit, the web portion of your repository.
These links provide a basic starting point for your team to prepare a comprehensive web site about your project.
After you get started on the project, you may want to replace these introductory paragraphs with a photograph of your team. Near the conclusion of your design project, you may also wish to include a photo of your finished product.
- Preliminary Project Plan Presentation - 10/17/07
- Final Project Plan Presentation - 11/5/07
- RP1 Wrap-up Final Meeting - 11/7/07
- Student Discipline Strengths for Staffing - 11/7/07
- Recruitment Commercial - 11/12/07
- Recruitment Commercial on YouTube
- RP1 Proposed Budget - 11/14/07
As you conclude the project, include links to all of your finished and fully polished documents here. The previous sections of the web site contain the entire design history of your project. This section contains the finished products. Add more links as needed.
Technical Conference Publication (SD II)
Poster Publication (SD II)
Managerial Design Review Presentation (SD II)