EEE 120 Capstone Design Project Spring
A car company has asked you to design the logic in the car to work with a new key fob. This is
for a car they plan to introduce in the fall . The new fob works a bit differently than most.
• If the key fob moves "far" from the car for two clocks, the car automatically locks.
• If the car is unlocked, and the user presses the button on the fob, the car locks.
• If the car is locked, and the user presses the button on the fob, the car unlocks.
• Whenever the car unlocks, the lights flash for one clock.
• Whenever the car locks, the horn beeps for one clock.
There are two inputs and three outputs:
Inputs:
S: 0 means the fob is near the car; 1 means the fob is "far" from the car.
B: 0 means the fob button has not been pressed; 1 means the fob button has been pressed.
Outputs:
H: 0 means the horn does not honk; 1 means the horn should honk
F: 0 means the lights should not flash; 1 means the lights should flash
L: 0 means the car is unlocked, 1 means the car is locked
You do NOT need to worry about the definition of "far" - another engineering team is handling that.
Note that you design MUST have a minimum of 5 states.
You will need to design two different state machines that satisfy the above requirements. Think about
different ways they might be implemented. Suggestions include how to handle the fact that the button
on the fob is pressed while the fob is far away. Does the car unlock? What happens if unlock and
lock directives conflict?
Come up with ideas on how you'd like to design the system. Interview three different stake
holders to discuss your ideas. Stake holders may be other students, TAs, UGTAs, or family
members. Be sure to document the names of the people you interview and their role. (That is,
their role as student, TA, UGTA, family member, etc.)
Once you go through this customer discovery, create two finite state machine designs applying
what you learned from your interviews and using different assumptions. This means
documenting the assumptions made for each design and going through the design process (State
Definition Table, State Transition Diagram, State Transition Table, Combinational Logic
Design). Note that the two designs you create must be functionally different. That is, you can't
create the same design once as a Mealy machine and once as a Moore machine. That is, the
assumptions you make must be different for the two designs. In addition, at least one of the
designs must be based on Karnaugh maps and logic gates. You will also need to incorporate
flip-flops with asynchronous set and reset.

NOTE: Use the same type of flip-flops used in the labs as they have asynchronous set and
reset!