3. What Is A VEX Robot?
• A system comprised of various
mechanical, electrical and
software constituents
• All parts are premade
• Can be modified and
manipulated
• A budget robot made from a
platform that enables students
to learn and apply various STEM
(Science, Technology,
Engineering and Math)
attributes.
4.
5. Challenges
• Closely related to the real
life challenges engineers
face every day
• Challenges would end up
governing how we would
construct our system
• We implemented various
system and management
processes to tackle these
challenges
7. Time
• 6 hours a day for 5 days
• Additional work would be done on our
own time without the physical robot to
refer to.
• Biggest challenge (in our opinion).
• It was a race against time!
8. Resources
• Us
• Mentors (Technical, Software, Project
lead, Project manager)
• Limited, but Various vex materials
• Any tools to help modify VEX materials
9. Budget
• Governed by our project manager.
• Determines the amount of materials
and resources.
11. • Although the SDLC
(System/software
Development Life-cycle)
model is tailored towards
software and
engineering, it can be
used in a variety of fields
aimed at accomplishing
a specific goal.
• Ours is the RSDLC
(Robotics System
Development Life-Cycle)
13. Objective
“Build a robot from the ground
up with VEX materials and
program the robot to run
autonomous to complete the
challenge. The two teams will
have the challenge to capture
their flag and return to their
starting positions.”
22. Build Challenges
• Using the least amount of parts to cut down
on cost, weight and time.
• Gravity combine with weight posed
problems on individual systems such as:
Chassis, Axels & Capture lift
• Create an efficient capture/lift system
• Create an efficient and functional drive train
23. Solutions
• Extended axels across chassis for
reinforcement
• Devised gears for capture/lift system
along with drivetrain
26. Challenges
• How to go from dead-
reckoning to
autonomous
automation
• Organizing functions to
make our system work
efficiently
• Program avoid function
to avoid objects
• Inexperience with
programming software
31. Solutions
• Trial and error
Manually inputting data into functions
• Calibration
physically measuring line sensor data
• More trigonometry
Finding arc length of tires instead of dead-reckoning
• Collaboration
Pitching solutions to mentors team members along with
the opposing team
32. Release/Play
• Demonstrate how we, as a team, have
integrated our STEM abilities
• We expect our robot to function correctly
autonomously
• Reveal how difficult it is to create an
autonomous system within a small time
frame
33. Analyze
• Reveal how we have been
able to work together to create
a fully functional system
• Re-think our weaknesses and
strong points as individual and
a team
• Re-think and find solutions to all
faulty aspects of our system
34. ThankYou…
Kumar and Mathabotics
Katlin, Frank and the B2E program
Our mentors: Alfonso, Ashley and Matt
Everyone who encouraged us to pursue
a path in engineering