EE 552 Project Proposal:
Automotive Monitoring System
Group: Korrey Scott 237118
Milton Mah 341428
Mike Holden 346386
Professor: Dr. Elliott
Date: January 20, 1998
1. Introduction
Our project entails the design and implementation of an Automobile Status Monitor (ASM). With the ASM, we are attacking the problem that many drivers are concerned about – one main display that contains the ability to view various system conditions. Through a very simple interface the driver has access to the vehicle’s attributes that are not normally viewable such as mileage, direction, and location sensors. Additional features that we may be adding include a clock, a thermometer, and a trip odometer. This project is very scalable because we will be able to add or drop features deemed necessary given the time constraints and complexity. Sources include EE 280 notes, EE 480 notes, our own course notes in this class, chip specifications, the Internet, and LED documentation. Depending upon the number of features we implement, additional sources as yet unknown may be employed.
2. Modularity and I/O
One of the most attractive features of this project is the ability to add or remove modules without having to redesign anything. The only module that cannot be removed is the one that produces the output to the LED display. All other modules can be easily integrated or removed from the final project. The following describes the function and I/O of each module.
2.1 Interface Modules
2.1.1 LED Display
Description: Displays the status of the selected module on up to four LEDs.
I/O: In order to use 11 segment LEDs, 4 output pins will be required for each LED. Having 4 LEDs requires 16 pins.
Pins: 16
2.1.2 User Buttons
Description: There will be three buttons that will serve as the interface to the ASM. One button will be used to cycle through the different modules, another two buttons will be used to set the clock.
I/O: Each button will have its own input pin to the ASM chip.
Pins: 3
2.2 Internal Modules
2.2.1 Mileage
Description: Calculates the vehicles current mileage. If the mileage module becomes selected the mileage is displayed on the LED.
I/O: In order to calculate mileage the amount of fuel in the tank needs to be known. We have elected to know the amount of fuel to an accuracy of 100 ml. To meet this accuracy for vehicle that holds less than 100 litres of fuel, ten input pins will be required.
Pins: 10
2.2.2 Expected Distance on remaining Fuel
Description: Calculates the distance the vehicle can travel with the amount of fuel in the gas tank.
I/O: All the information needed for this calculation can be accessed from the mileage module.
Pins: None
2.2.3 Direction
Description: Shows the direction that the vehicle is currently moving.
I/O: Requires a 3 – bit input that represents 1 of 8 directions.
Pins: 3
2.2.4 Speed
Description: Displays the current velocity of the vehicle.
I/O: Speed is given to the chip as an 8 – bit number. Can represent speeds between 0 and 255 km/hr.
Pins: 8
2.2.5 Trip Odometer
Description: Displays trip odometer up to 9999 km, accurate to the nearest km.
I/O: Trip odometer can be calculated using the speed module. No input is required.
Pins: None
2.2.6 Clock
Description: Displays time in the hh:mm format. Time can be set using buttons from interface module.
I/O: If available, could use an external clock signal to determine time.
Pins: 1
2.3 Other Modules that could be include
2.3.1 Temperature: Display temperature of environment outside of vehicle.
2.3.2 Vehicle Utility Status: Battery power, fluid levels, engine temp, tire pressure etc.
2.3.3 Location Warning: Warns the driver when an object is within a certain distance. A sound is made and the location on the car shown on the LEDs.
2.3.4 Carbon Monoxide Warning: Warns the driver when CO levels have reached toxic levels.
2.3.5 Other Warning Systems: Warnings when door open, hood open, trunk open or when tire is flat.
3. Expected Hardware
3.1 Chip
We are currently planning to use the Alterra board, which is a reprogrammable FPGA. We intend to test our chip by building the system on a board and using switches and pushbuttons to simulate our design. We do not need RAM or a microprocessor for this implementation. In our preliminary design we will be using 41 I/O pins.
3.2 Other Hardware
3.2.1 LEDs: We are planning to use four 13 segment LEDs. The LEDs will be used to display numbers 0 to 9, letters N, NE, NW, E, W, S, SE, SW plus any other combinations of words, letters or abbreviations.
3.2.2 Buttons: We are planning to use three buttons for this project. One will be used to go around the main circle in figure 1. The other two will be used for setting the clock and resetting the trip odometer.
4. Time Management
|
Person |
Task |
Deadline |
Duration |
Test/Debug |
|
Group |
Project Specification |
Feb. 3 |
12 hours |
None |
|
Group |
Resource Requirements |
Feb. 24 |
8 hours |
None |
|
Group |
Simulation Documentation |
Mar. 10 |
14 hours |
None |
|
Group |
Final Report |
April 7 |
18 hours |
None |
|
Group |
Oral Presentation |
April 7, 9 |
6 hours |
None |
|
Group |
Student Application Notes |
April 9 |
7 hours |
None |
|
Mike |
Clock Design |
Feb. 28 |
25 hours |
15 hours |
|
Milton |
Interface Design |
Feb. 28 |
25 hours |
15 hours |
|
Korrey |
Mileage Module |
Feb. 28 |
10 hours |
4 hours |
|
Korrey |
Expect Distance Module |
Feb. 28 |
7 hours |
2 hours |
|
Korrey |
Direction Module |
Feb.28 |
2 hours |
2 hours |
|
Korrey |
Speed Module |
Feb. 28 |
2 hours |
2 hours |
|
Korrey |
Trip Odometer Module |
Feb. 28 |
4 hours |
5 hours |