Sie sind auf Seite 1von 10


Aastha Gupta (03/EC/14)
Anshuman Chhabra (31/EC/14)
We base our 8085 project for the EC-316 Microprocessors Lab on building
collision detection and fuel management utilities for cars. The functions of making
cars more interactable with their environments are infinite and a few cases and
examples have been developed by us in the next section. Moreover, the idea for
the project cannot be - and should not be, attributed to us, as it was Prof. Gadre,
our teacher, who nudged us in the right direction with regards to making the car
seemingly “Smart”. We had initially thought of a proximity detector to prevent
collisions in cars but a collision detector (along with the fuel management system)
would better utilize the 8085 and lead to a better project overall.

Smart Car, Collision Detection, 8085 Microprocessor, Fuel management, Vibration
detection, Peripherals, Interfacing.

EC316 Microprocessor Lab Project

ECE Division
Netaji Subhas Institute of Technology
New Delhi 110078
Introduction and Motivation -
The basis for this project is simple. There is a dire need for technologies to
become “Smart”, in that they should be able to interface with mobile devices and
should provide utility functions much more than what they have been specifically
designed for. This extends to cars too – Most cars have still been devoid of the
Internet of Things (IoT) wave, and providing intelligent communication between a
vehicle and the driver has not received widespread attention from scientists and
engineers alike. For this reason, we wish to provide some “intelligent”
functionalities to the working of the future “Smart Car” and thus set two goals for
the satisfactory completion of our project:

1. Collision Detection: Car collisions are very bad. But they are worse when one
gets embroiled in an insurance hassle due to lack of witnesses as well as other
such similar scenarios. Consider these examples -

Case 1. You are driving in your car in the right lane. However, a person is driving
on the wrong side on the same lane and collides with your car. You call the police
to set the issue straight by filing an FIR. However, due to some political or
relational connections of the person with the police and other positions of
authority, you are told that this is not such a big deal and that an FIR would only
bring you trouble. It is better to take a measly sum as compensation from the
wrongdoer and then be on your way. This could relate to similar problems when
insurance has to be claimed after an accident. This is quite a widespread problem.
Would it not be better to have actual proof of the collision as well as an intensity
meter coupled with a display that shows time of accident?

Case 2. You have parked your car and have gone to the market to buy groceries.
You complete your shopping and come back to your car and then drive away. It is
only a week later that you realize that your parked car had been hit by a novice
driver a week ago when you had gone grocery shopping. Would it not be better to
have had a collision detector meter which would have continuously beeped after
a collision and displayed the intensity of the hit along with the time the collision

Case 3. You have been in a terrible accident and you are in need of an ambulance.
In such a scenario, it is necessary to alert people nearby to help you as well as
help them call an ambulance as soon as possible. Would it not be better to have a
beeper after a collision and also house ambulance numbers that can be displayed
if the intensity of the collision is above a certain threshold?
This is the motivation behind our project and we set about trying to meet the
aforementioned needs of the collision detector using the 8085.

2. Fuel Management: Most people who own a vehicle never really know how
much fuel was consumed by the car on a particular day. There is only a vague idea
with which people get about travelling in cars. Thus, we propose a fuel
management system using the 8085 by which a user can input a date and his/her
fuel consumption on that particular day is displayed for better management.

We thus seek to leverage the Intel 8085 microprocessor to help us achieve both
these goals. The rest of the proposal is structured as follows – the next sections
list how we went about decoding the problem and segmenting it into different
steps. This is better visualized in the form of a block diagram as we show. We also
present a flow chart assessing the functions and the logic behind the software and
the hardware. A Gantt chart is shown to show the timeline and distribution of
work amongst ourselves.


The basic idea behind the logic we employ to achieve a solution for the problem we mentioned earlier is
this -

1. We first use the vibration detection module to give us an indication as to whether something
resembling a collision has happened or not.

2. Next, if a collision has happened, we use the output from the accelerometer to adjudge the intensity
of the collision.

3. Using this newly obtained value, we make sure that if the accident is serious, the circuit creates
enough noise to attract people nearby and furnish useful information, like ambulance and hospital

4. If the accident is not serious, only the intensity and the time is displayed for reference. We will display
the time by reserving 4 locations in the RAM (battery powered), which will keep increasing. When the
collision occurs, an interrupt will service these locations to output the current time.
Anticipated BOM :

1.Intel 8085 IC
2.Support IC : 8279 (Programmable Keyboard/Display Interface)
Used to ->
a.) Scan the keyboard, detect the key pressed and then transmit the information
to CPU.
b.) Output data from CPU to display peripherals.
3. LCD
4. Buzzers (Piezo Speakers)
6. SW-420 Vibrational Sensor
7. Jumper cables
8. 8KB ROM
9. 8KB RAM
10. Keypad


1. 8085 Microprocessor by R. Gaonkar

S.K.Sen_.pdf -> 8085 Microprocessor and Peripheral ICs by S.K. Sen