Engin 103
Project 2
Good Design: Predictability
of the “hill performance” of a vehicle
Predictability and reliability are
certainly two necessary features of a well-designed machine. This can be
achieved by eliminating or minimizing all components that may lead to
unpredictable behavior. The simplest design that can perform the required tasks
should always be in the short-list of candidates for a prototype. On the other
hand, common machines require humans as operators, and humans as complex
systems work under the influence of many factors that easily lead to
unpredictable behavior. Minimizing human intervention,
ideally to an intelligent ‘digital” response of yes/no, helps restore predictability.
I used to drive a long distance on a regular basis, by using highways,
very-low-traffic schedules, and cruise control, my
total travel time could be predicted within 1% of error.
In this project, you are required to
work in teams to demonstrate its predictability of the performance of a vehicle
on a hill. The hill will be represented by a 1m ramp that has a variable angle.
The goal is to predict how far the vehicle will get in 2s for certain ramp angle.
A calibration needs to be done using data modeling to make this type of
prediction. Each team should present in both days to receive full credits awarded
to project completion and presentation (see credit table below).
In this project, the vehicle could
be a commercial toy one or built by the team, the focus will be on
predictability, and an important effort will be dedicated to the analysis and
calibration of the vehicle performance in the sense described above. The team
will use data modeling or curve-fitting (see CW 3 and 4) with Excel (© by
Microsoft) to make a model of the car performance on the ramp and subsequent
predictions. If you can do a calibration of your vehicle performance using data
modeling, then it is predictable. The calibration using data modeling is
device-specific, it needs to be redone if any change
has been made to the vehicle or ramp.
Total materials cost should be less
than $30, copies of receipts to be submitted with project reports.
Each team will do a 5 minute
presention on their device in each of the two presentation days. In the first
day, the teams will give an introduction (what they did, how they achieved
predictability, etc.) followed by the demonstrations. In the second day,some extra factors that may affect the performance
predictability such as dust or other slippery materials on the ramp. The
webpage on the project, along with the project report will be due the class
after the second day of the presentations (please check the e-syllabus for
exact dates). A progress report on the project will be due about a week before
the first of the two presentation days (please check the e-syllabus for exact
date). The project report is expected to be a good written document (see Good Writing
Practices), and graded under three categories: correct grammar and neat
presentation; logical arguments and structure; accurate report of the team
project, completeness, and no plagiarism. Project report will be submitted in
hardcopies with member signatures and also in electronic form (see Computer Files:
Names and Electronic Submissions). A complete report should include the
following sections:
-Introduction: brief description of
project objectives in your own words, background information needed for the design
with emphasis on predictability of the “roulette of fortune”, work distribution
among the team members, and timelines for the different parts of the project:
research, design, building, analysis/calibration.
-Design and building: this section
should include sketches and diagrams: how the different design elements and
hardware components were selected enhance the predictability of the “roulette”,
the list of components with specification and prices.
-Analysis/Calibration: should
include data obtained from your device: tables of starting force and resulting
rotations, insert of Excel worksheet with discussions of different types of
function relating those two variables and pinpointing which function is the
best (with the smallest “standard deviation”, see CW 3 and 4). It should also
include results from testing the prediction made by this model and an
assessment of the predictabily of your device. It should also include a brief
manual of operation, troubleshouting list, and appropriate recognition of other
author’s materials if used in your project.
-Conclusion: overview of the team
achivement and lections learned for the future.
Grades will be computed as follows:
Items |
Points |
||
Project
completed, if presented both days |
50 |
||
Project
performance (performed specified tasks) |
10 |
||
Good
design (predictability: existence of a function relating starting force to
resulting rotation) |
10 |
||
Project
presentation and webpage |
10 |
||
Written
reports |
Progress
report |
5 |
|
Project report: will not accepted without all member’s
signatures on percentage of participation |
Grammar
and presentation |
5 |
|
Logical
arguments; structure |
5 |
||
Accurate
and complete |
5 |
||
Total
project grade |
100 |