P10201: LV1 Platform Integration (Land Vehicle 1 Platform Integration)
/public/

Planning

Table of Contents

Mission Statement

Product Description/Objective Statement

To integrate current and future RP1 motor modules and motor controllers while improving previous robotics platform design in order to meet all required customer needs.

Key Project Deliverables

Key deliverables for this project include a robust land vehicle platform design that can be easily manufactured in lots of 1-10.

Primary Project Opportunities

Primary opportunities for this project include educational applications for first year students, a wide range of faculty and graduate research projects, and sales of kits to the public at large. This project also provides the opportunity to showcase the engineering talents of RIT students to companies interested in hiring them.

Assumptions and Constraints

It is assumed that this will be a wheeled vehicle that can traverse a variety of terrains and be assembled from modules to form a variety of configurations.

Stakeholders

Stakeholders for this project include the Kate Gleason College of Engineering at RIT, faculty and graduate researchers, current and future senior design teams, students interested in the multi-disciplinary robotics club or FIRST robotics, and the student body as a whole.

Customer Constraints

The base level constraints placed on the project by the customer, as defined by the project family track can be found here.

Preliminary Customer Needs

Platform Integration
  • Must interface with Gen 2 and newer motor modules and motor controllers.
  • Must look professional and well-organized.
  • Must be lighter than the previous generation.
  • Must provide a means to secure a 1kg payload.
  • Must be equal in size or smaller than the previous generation.
  • Must be easy for a first year engineering student to assemble and use.
  • Must be stable on a flat surface (i.e. tabletop) throughout its operating range for a variety of payloads.
  • Must be faster than the previous generation.
  • Must be open source (all documentation published).
  • Must be open architecture (COTS parts used).

Function Tree

LV1 Platform Integration Function Tree

LV1 Platform Integration Function Tree

Required Resources

People Capital Environment
  • Faculty Guide
    • Dr. Wayne Walter (ME)
  • Faculty Consultant
    • Prof George Slack (EE)
  • Graduate Teaching Assistant
    • TBA
  • Primary Customer
    • Dr. Ed Hensel (ME)
  • Approximate $1000 LV Project budget
    (to be split between P10201, P10202 and
    P10203 upon discretion of teams)
  • All existing RP hardware including
    RP100, RP10 and RP1 robots
  • All existing RP project documentation
  • Mechanical Engineering machine shop
  • Brinkman Laboratory
  • Senior design floor
  • Electrical Engineering laboratory

Staffing Requirements

Name Discipline Role / Skills
Dr. Wayne Walter Electrical Engineering Faculty Guide, Will work closely with the team on an on-going basis to facilitate success.
Prof. George Slack Electrical Engineering Faculty Consultant, Will provide discipline technical support on an intermittant basis.
TBD Grad Student TBD Teaching Assistant
TBD Student Electrical Engineering Student Responsible for interface and electrical connection between motor modules and platform
TBD Student Electrical Engineering Student Responsible for interface and electrical connection between motor controller and platform
TBD Student Electrical Engineering Student Responsible for general layout and connection of electrical components on platform as well as wiring layout
TBD Student Mechanical Engineering Student Responsible for mechanical interfacing with motor modules
TBD Student Mechanical Engineering Student Responsible for mechanical interfacing with motor controllers
TBD Student Mechanical Engineering Student Responsible for main structural analysis and design of platform as well as payload interface

Preliminary Work Breakdown Structure

Week 0->1 Tasks Week 1->2 Tasks Week 2->3 Tasks
  • Team Introductions
  • Review project readiness package created in DPM
  • Meet with faculty Advisor/Consults and Customer
  • Meet with P10202 and P10203 project groups

Assignments:

  • Begin learning EDGE server
  • Download and become familiar with SVN Client
  • Load contact information to EDGE
  • Begin research on RP project family
  • Schedule weekly meeting between P10201, P10202 and P10203 project groups
  • Conduct formal interviews with stakeholders and customers
  • Review preliminary customer needs
  • Analyze previous RP hardware
  • Meet with P10202 and P10203 project groups

Assignments:

  • Consider task placement for team members
  • Continue background research
  • Post updated information to EDGE server
  • Continue analysis of previous RP hardware
  • Refine and finalize customer needs
  • Meet with P10202 and P10203 project groups
  • Begin brainstorming preliminary design
  • Assign team member specific tasks
  • Plan weeks 4-11

Assignments:

  • Begin work on specific tasks
  • Continue background research
  • Continue brainstorming
  • Schedule followup stakeholder and customer interviews

Risk Assessment

Description of Risk Possible Consequences Probability of Risk (H/M/L) Severity of Risk (H/M/L) Overall Risk (H/M/L) Contingency Plan
Team member missing for extended period of time Components may be missing from final project M M M Delegate times to meet and update all members on status of specific areas of research, good documentation
Parts/Materials Arrive Late Delayed assembly and testing period, possibly miss deadline for completion H M M Design module so process does not hinge on ordered parts. Cite multiple vendors for same components
Platform causes decreased performance of land vehicle Speed, Stability and/or Weight do not meet customer requirements L H M Weigh customer requirements highly during design process
Platform drives land vehicle cost up Too few land vehicles are produced to meet project specs M H M Pitch project family idea to investor with more capital
New platform fails to integrate with concurrent and past projects No working vehicles can be produced L H M Hold regular meetings with concurrent teams to ensure integration, and base all designs off of older components

Additional Documentation

Home | Planning | Concept Development | Chassis | Base Plate | Power Supply | Payload Adapter