Title : Schematic Diagram of Project

METHODOLOGY (3)

CONTENT:

This is schematic diagram of my project, referring of the block diagram, I have done this schematic diagram completely. It was done almost 2 weeks with others helped. To design this schematic,I have used Protel software. After completing this schematic diagram, so I can continue with others part such as converting schematic diagram into PCB layout to make it easy to print on the covered of sticky paper, and then the PCB layout printed need to be iron on PCB board. The last step is etching by using FERRIC III CLORIDA ACID. After etching also have another stage but I will explain it at others post.

OBJECTIVE:

1.) To identified what component to be use by referring of the block diagram and then design it on Protel software to run it.
2.) To make sure all component can be interface for each other and function.
3.) To trace any error occurs.

TITLE : CHANGING OF BLOCK DIAGRAM

SEMESTER 2/2012 (FYP SEM 2)

METHODOLOGY (2)

CONTENT: 

I have done some changing due to my block diagram, this is because depending on availability of my project. And also because of components that more suitable than previous. But the flow of operation stills the same. For the new block diagram, I have changes components such as infrared LED and phototransistor to rotary sensor. I have use 4 rotary sensor to detect the current speed. For rotary sensor 1, its will detect the speed at 90km/h and display on LCD. Rotary sensor 2 will detect the speed for 100km/h, rotary sensor 3 will detect the speed at 110km/h and the last one is rotary sensor 4 will detect the speed at 120km/h and display on LCD. I have to do some changing on this project because of the program, I can’t code the program to display the speed one by one. For example, I can’t display the speed on LCD like 100km/h, 111km/h, 112km/h, 113km/h…..and so on. It’s too hard to code the program like that and to interface with the mechanical parts it’s the problems. So I just can display the speed on LCD like this 90km/h, 100km/h, 110km/h, 120km/h. For the rest part, I still use the same process but have a little improvement at the first warning stage that is when the bus reaches the speed at 115km/h, from the previous one, I just make it at that speed yellow LED will blinking, and LCD display the current speed 115km/h. But for the improvement, I have add a buzzer to triggering along the speed, that means if the driver not slowing down the speed below 115km/h, the buzzer will triggering nonstop. But if the drive slow down the speed and the buzzer will stop triggering. This warning such as the Honda system, so I got the idea and put that on my project as upgraded.

OBJECTIVE:

1.) To make it more suitability to interface with mechanical parts. 

2.) To reduce any error either in the program and hardware parts.

3.) To make it easy to control.

CONCLUSION:

From this changing, I can done it in a simple of features but still the same purposes. This changing is to make my project become more clearly to others.