AME 3623: Project 8: Lateral Velocity Control
For the last two projects, you have developed the proportional error
and derivative error control pieces. In this project, we bring these
two pieces together and tune the parameters so that the craft will
orient to and stay at a goal orientation.
- All components of the project are due by Thursday, April 20th
at 9:00 am
- Groups are the same as for project 1.
- Discussion within groups is fine.
- Discussion across groups may not be about the specifics of the
solution (general programming/circuit issues are fine to
At the end of this project, you should be able to:
- integrate lateral velocities as sensed by the cameras into the
control loop (implementing a velocity control law).
Component 1: Hardware
There are no new hardware components for this project. However, we
are assuming that orientation control is working well and that you
have your cameras working properly.
Component 2: Software
Implement the following functionality:
Component 3: Looking Forward
In class, we will be discussing the implementation of FSMs in C code.
For project 9, we will move the sequencing code to a fsm_task.
For this project, you may take this step preemptively.
For project 9, we will be using the distance sensors. We recommend
that you mount one pointed forward and the other pointed to either the
left or right. We will be providing new distance sensor mounts that
will allow you to mount the sensors on the front of your hovercrafts.
What to Hand In
All components of the project are due by Thursday, April 20th at
- Demonstration/Code Review: All group
members must be present.
The demonstration must be completed by Tuesday, April 25th.
- Check in the following to your project 8 area of your
- Personal report: There is no personal report due for this project.
Personal programming credit:
Group grade distribution:
- Each person must accumulate at least three personal programming
credits over the course of the semester. This project offers
- To receive credit, you must be the primary designer,
implementer and debugger of the component. This does
not mean that your other group members should not be looking
over your shoulder. But: you must do the "driving."
- 35%: Project implementation
- 30%: Demonstration of working project (to either
of the TA or the instructor)
- 35%: Documentation
Group Grading Rubric
Grades for individuals will be based on the group grade, but weighted
by the assessed contributions of the group members to the non-personal programming items.
andrewhfagg -- gmail.com
Last modified: Thu Apr 13 10:20:55 2017