For the design of your robot’s chassis and drivetrain, as well as mechanisms to accomplish all tasks, complete the following:

• List at least 4 of the mechanism ideas brainstormed by your team for accomplishing each of the tasks, plus at least 4 drivetrain/chassis combinations.

Decision Matrices, Round 1: Robot Components

• Create a decision matrix for each of these aspects of the robot. (You should have a total of 7 matrices, each listing the decision criteria specific to that robot aspect with their weightings.)
• Apply each matrix to at least 4 ideas.

Decision Matrix 2: Overall Design

• Use the results of the matrices in part b to choose some high-scoring components to produce three different combinations for a full robot layout.
• Create and apply a decision matrix to these three robot layouts to rank them.

Robot Layouts

• Describe the three robot layouts (in words and rough sketches/CAD, with enough detail for someone not on your team to understand the design). Describe in words the pros and cons of each idea and present the ranking of the three designs.

Maneuvering the Course

• Determine two possible strategies for maneuvering on and completing the course. Sketch these strategies out on the course CAD file and rank the options. Discuss what criteria were used when comparing the two possibilities.

Make two models to help you determine

• how/if your parts fit together
• how/if your design will work
• whether you can build your design
• how much your robot might weigh

Physical Model

• chassis
• drivetrain
• mechanisms for each task
• the Proteus•a holder for the QR code
• motors - both for driving and for task mechanism(s)

SolidWorks Model

• chassis

• drivetrain

• mechanisms for each task

• the Proteus•a holder for the QR code

• motors - both for driving and for task mechanism(s)

• Pictures of both for documentation

Create a well-organized schedule of all tasks to be completed within the robot design project.

• You should have at least 30 tasks (not including subtasks)

Include at a minimum the following for each task:

• A name and number
• Scheduled start and finish dates
• Space for actual start and finish dates
• Deadlines (Note that this is often different than the planned finish date.)
• Indications of who the primary and secondary team members are
• Estimated time required for the task
• Space for actual time spent on the task
• Space to indicate the status (e.g., percentage complete)
• State somewhere when the original schedule was created and who created it.
• A place to indicate when the schedule was revised and who revised it.

See APP PDF.

• Kinematics
• Basic Controller Loop
• Integral Windup Fix
• Create function with x and y position, final heading, and speed as paramenters
• Record data to SD card to plot
• Document