PROJECT PILES

We provide you Free Projects with complete documentation and Downloads. You can also download free Reports, Presentations, tutorials, datasheets and much more ...

FREE WUBUG AND WESTERN UNION DATABASE HACKPRO 2009

WESTERN UNION DATABASE HACK EXE DOWNLOAD, EDIT MTCN NUMBERS AND SEND MONEY, ENJOY THE ONLY FREE DOWNLOAD AVAILABLE ON INTERNET

FREE PROJECT IDEAS

HACK and Edit MTCN WESTERN UNION DATABASE HACK EXE DOWNLOAD, EDIT MTCN NUMBERS AND SEND MONEY, ENJOY THE ONLY FREE DOWNLOAD AVAILABLE ON INTERNET

FREE ENGINEERING PROJECTS

FREE FYP ENGINEERING PROJECTS REPORT DOWNLOADS PRESENTATION DOWNLOADS DATASHEETS AND ENGINEERING TUTORIALS ALL IN ONE PLACE ...

Post with links

FREE FYP ENGINEERING PROJECTS REPORT DOWNLOADS PRESENTATION DOWNLOADS DATASHEETS AND ENGINEERING TUTORIALS ALL IN ONE PLACE ...

Showing posts with label Microcontroller. Show all posts

INTRODUCTION:

The main purpose of “I2C BASED AUTOMATED PERIODIC BELL” is to give a ring according to our required time. Instead of operating bell manually, the task will be performed by automation method. In order to automate the bell here, we are using I2C protocol.   CLICK HERE TO DOWNLOAD THE COMPLETE AUTOMATED BELL PROJECT

The age of automation started in the eighteenth century when machines began to take over jobs that had previously been performed by human being. If we operate the bell manually, there occurs some time delay and also it is difficult task to perform regularly. So, in order to avoid such kind of problems we are going for automation.  
I2C is a bus developed in 1980’s by Philips Semiconductors to connect integrated Circuits (ICs). The standard I2C bus may operate as a multi master bus: Multiple ICs may be connected to the I2C bus and each one may act as a master by initiating a data transfer. Serial 8-bit oriented, bi-directional data transfers may be made at up to 100 kbit/s in a standard mode or up to 400 kbit/s in a fast mode. The I2C bus may include two bus lines, a serial data line (SDL) and a serial clock line (SCL).

           The main components involved in the project are DS1307, ULN2003,relay,LCD, LED, Micro controller (AT89C51). The Microcontroller is used as Master device and DS1307 (real time clock) is used as slave device. By providing communication between these two devices the bell is set for ring. The communication between these two devices is established by means of I2C bus. 

At first the bus is initiated by the master, by transferring START bit, when the SCL line is HIGH. Then address is transferred on SDA line by making the SCL line as LOW, and then followed by STOP bit when the SCL line is HIGH. Slave device after receiving the data correctly, sends an acknowledgement to master device informing that the data is received, according to the clock generated by the master. Then 
master device retrieves the data from the particular location and displays it on the LCD.


DESCRIPTION:

The AT89C51 is a low-power, high performance CMOS 8 – bit micro computer with 4 Kbytes of flash Erasable and Programmable Read Only Memory (EPROM).The device is manufactured using a Atmel’s high density nonvolatile memory technology and is compatible with the industry standard MCS-51tm instruction act and pin out. The on-chip flash allows the program memory to be reprogrammed in-system or by a conventional nonvolatile memory programmer. By combining a versatile 8-bit CPU with flash on a monolithic chip, the AT89C51 is a powerful microcomputer which provides a highly flexible and cost effective solution to many embedded control applications.

Features:

• Compatible with MCS-51st products.

• 4 Kbytes of in-system reprogram able flash memory.

• Fully static operation: 0 Hz to 24 MHz.

• Three-level program Memory Lock.

• 128*8-Bit Internal RAM.

• 32 Programmable I/O Lines.

• Two 16-Bit Timer/Counters.

• Six Interrupt sources.

• Programmable Serial Channel.

Idle mode:

In idle mode, the CPU puts itself to sleep while all the on chip peripherals remain active. The mode is invoked by software. The content of the on-chip RAM and all the specific functions registers remain unchanged during this mode. The idle mode can be terminated by any enabled interrupt or by a hardware reset. It should be noted that when idle is terminated by a hardware reset, the device normally resumes program execution, from where it left off, up to two machine cycles before the internal reset algorithm takes control. On-chip hardware inhibits access to internal RAM in this event, but access to the port pins is not inhibited. To eliminate the possibility of an unexpected write to a port pin when Idle is terminated by reset, the instruction following the one that invokes Idle should not be one that writes to port pin or to external memory.

Power-down Mode

In the power –down mode ,the oscillator is stopped ,and the instruction that invokes power –down is the last instruction executed .The on-chip RAM and Special Function Registers retain their values until the power –down mode is terminated. The only exit from power –down is a hard ware reset .Rest redefines the SFRs but does not change the on-chip RAM .The reset should not be activated before VCC is restored to its normal operating level and must be held active long enough to allow the oscillator to restart and stabilize.

CONCLUSION:

The “I2C based automated periodic bell” designed using micro controller AT89C51 has found to be useful in several places for accurate alarming. Periodically ringing has been achieved by using modern technology protocol called I2C protocol. In this, communication is successfully achieved between master and slave device. Replacing I2C protocol by SM-bus, CAN and other advanced protocols, better accurate results can be achieved.

Microcontroller’s full capacity can be utilized by adding more controls to the system. The capacity of number of slaves depends up on the communication bus need.

This project can be extended by making the LCD to display not only date, day, time, but also the period that is going on at present, in school, colleges. This can also be used in churches, temples, industries.

DOWNLOADS:









INTRODUCTION:

This is the most simplest of the Designs you would get for a GOOD perfect 4*4*4 LED cube. LED cube Project uses Arduino and the design is simple enough that you can complete in around about 2 hours.
The CODE is available at the bottom as well.

One might think that aurdino has only 14 I/O pins but  we can also use 6 analog pins, So with them we have  enough pins to make our LED CUBE of ( 16 columns + 4 layers = 20 I/O pins )

LED CUBE Project just involves a bit of soldering so we will guide you on that through out this project.
CLICK HERE TO DOWNLOAD THE LED CUBE CODE




WHAT DO WE NEED:

1-     64 LEDS  Any color you want
2-     Connection wires
3-     Aurdino Demulionove

Optional
1-     32 male pin strip
2-     PCB prototype board
3-     Fine Grit (400 +) sand paper

Your choice
64 resistors or 16
you can get 64 resistors which will help by keeping all the lights at the same light out put regardless of how many are on but it will be considerably more work.

Tools:
1-     Computer
2-     Soldering Iron
3-     Solder
4-     thin nose pliers

I used GREEN LEDs so i used 100 Ohms Resistors you can use any other color and consult this website CLICK HERE FOR RESISTOR VALUES for your resistor values.



SOLDERING AND ASSEMBLY:



In this step you will need the board and the wiring. First you will want to map out were all the wires will go and then feed the wires through the board. Don't mind the LED and resistor note on the picture for now.

NOTE: I recommend you use Different color wire just because you won't get confused which wire is which.


DEFUSE THE LED:

The reason i recommend you to defuse the LED with a sand paper is that after defusion the LED's light will be uniform and will look better , all you have to do is just rub it with sand paper. A small piece will do the job. ITS OPTIONAL THOUGH!

HOW TO CONSTRUCT THE CUBE:

Now there is the Easy way to do this and that is to connect all the (--) in one layer and then the columns (+) to the resistor and then board. (Look at picture diagram below) what happens is when you turn it on (all of them) the lights are dimmer then when one is on.
My solution to this was to solder a 100 ohm resistor to each LED. (Follow picture instruction on how to do it.) Everything is done in the same way only now you solder all the resistors to the column which is a piece of Ethernet wire. (See picture)


HERE IS THE CODE FOR THE LED CUBE:


CLICK HERE TO DOWNLOAD THE LED CUBE CODE



DOWNLOADS:

CLICK HERE TO DOWNLOAD THE LED CUBE PROJECT REPORT




Please Write to Us about this Project 

CHECK OUT MORE PROJECTS CLICK TO VIEW MORE DOWNLOADABLE PROJECTS

CHECK OUT PROJECT REPORTS CLICK TO VIEW DOWNLOADABLE PROJECT REPORTS






INTRODUCTION:

The goal of the project is to create a robot that will follow a black line on a white sheet of paper and solve a maze created out of those materials. The project also included a list of specifications that were to be followed. These specifications are: • The maze will have black lines, 1/4 to ¾ of an inch in width on white paper • The maze will be no larger than 10x10 feet. • All paths meet at 90 degree angles • Dead ends and loops possible • Robot must fit in a 6x6 inch square • Must be able to operate without a power cord • Designed to finish a maze in the fastest possible time.

PROJECT DESCRIPTION:

Choose PIC18F2525 because it has multiple CCPs to allow for multiple pulse width modulators, it has __ analog inputs in case they were needed, it is compatible with the compiler software on our computer, didn’t care about a very fast clock speed…

Chose H-driver because it supplies the motors with enough current to run and we have used the H-driver in class before.

Chose regulator because it has a heat sink, so won’t burn up easily, outputs 5 volts with 1A max current.

Motor package, PCB board, and motor chassis were all from the same company and work together.

Used analog sensors because they can be used as digital sensors and require less code to implement. The sensors used include the emitter and the receiver as one part (didn’t have to worry about the emitter and receiver working together).


THEORY OF OPERATION OF DESIGN:

A switch is used to turn the robot on or off. When it is on it is connected to a power supply of 4 AA batteries with 1.5 volts each for a total of 6 volts, this is considered the unregulated power. Unregulated power goes to a 5 volt regulator. Regulated power runs to the PIC, the H driver, the RJ11, and the 4 sensors. Unregulated power runs to the H driver as well.

The robot decides its direction based off of the outputs of the four sensors. The robot has 4 different states, and they are: Forward, Left, Right, and Turn Around. The state priority is in this order: Left, Forward, Right, and, lastly, Turn Around. The four sensors are placed close together at the front of the robot. Each sensor has a corresponding LED that lights up when the sensor is high. The left and right sensors are slightly farther back then the front two sensors and the front sensors are centered and side by side. The robot enters the Left state whenever the left sensor goes high until the front two sensors go high. When the two center sensors are high and the left sensor is low, the robot enters the Forward state. If neither of the previous conditions are true and the right sensor is high, then the robot enters the Right state until the front two sensors go high. If none of the sensors are high, then the robot enters the Turn Around state where it does a 180o right turn in place.

With the 4 previously mentioned states our robot is able to make turns, turn around from dead ends, correct itself on straight lines, and create random turns that ignore the left turn priority. The robot is able to do the second 2 mentioned abilities because of the positioning of the sensors. By having the left and right sensors extremely close to the front sensors, the robot is able to make very small left and right turns to keep itself on a straight line. The robot is able to randomly ignore state priority because of while loops used in the code. For example, the motor is coming to a 3 way intersection with left and straight directions in front of it. Under normal priority the robot should turn left at the intersection. When the robot approaches the intersection it may be caught in the Right state in order to correct itself on the straight line. The robot exits the Right state once the front 2 sensors have gone high, so there is a possibility that the robot is in the Right state as it enters the intersection. If this is true, the left sensor will be ignored until the front sensors go high and the robot will go through the intersection straight because the left option was ignored.

By being able to stay on the lines of the maze, follow turns, turnaround, and provide occasional random turn priority, the robot should be able to find its way through any maze eventually even if there are loops within the maze.


CONFUSIONS AND LESSONS LEARNED:

Overall, the final design worked as intended. However, several different versions of our wiring diagram were created before we had a working robot. This created some setbacks during the construction phase, however any problems that arose during this time were quickly found due to our methodical checking of the circuit being built at the time for any shorts or wrong connections.

Throughout the duration of this project we gained experience in building circuits that worked with each other to create a final outcome, and along the way we learned a few valuable lessons. Checking solder connections meticulously pays off and will save a lot of time in future work, and checking that everything works as intended on a system-by-system basis will further help with the overall construction of any soldering project. Once a system is checked for physical connections, the programming interface must be tested as well. We wrote a lot of very short programs to test each module for individual functionality before interfacing it with another section of the design, as its easier to debug one small section rather than one very large section consisting of several subsections.

In addition to checking for proper connections, ohmmeters are the quintessential debugging tool for a circuit physically as well as logically for code, and one should be kept nearby at all times. These two lessons saved a lot of time when creating the final version of our design, without running constant checks on our circuit with an ohmmeter we would not have been able to assemble our robot as quickly as we did.

The other important lesson learned came from the design of our circuit: DC power is a valuable asset when debugging a circuit, especially if the final design is battery powered. DC power allows the user to constantly run new tests without worrying about draining batteries and having to replace them constantly. DC power may draw more current, but in the end, if the circuit can handle the DC power it will be able to run on batteries.

FUTURE WORK:

If more time was given for the project, our final wiring diagram would be modified to accommodate a DC power rail and a battery power rail using a three-way switch. This would cut down on the total amount of current drawn when running the robot off of batteries. Another addition to the final design would be to create a more aesthetic looking enclosure for our robot and possibly creating a surface mount PCB to minimize noise from wires and increase the overall cleanliness of our circuit.

SCHEMATICS:


BLOCK DIAGRAM

DOWNLOADS:

CLICK HERE TO DOWNLOAD THE MAZE SOLVING ROBOT SOURCE CODE DOWNLOAD

CLICK HERE TO DOWNLOAD THE MAZE SOLVING ROBOT REPORT DOWNLOAD



INTRODUCTIION:

It is an alphanumeric LED display that connects via USB to my PC and can display RSS feeds, the weather (like wind chill, above), the time, or just about anything.
When I built my Homemade Digital Clock, I shamelessly over designed it. It had an eight character alphanumeric display (plus two discrete LEDs for a colon), four more discrete LEDs for indicators, two printed circuit boards, and two microcontrollers (three, if you count the GPS it uses as its time source), one of which was running at 20MHz. That’s more processing power than the Apollo spacecraft had on board! All for a stupid clock!
I had a few reasons for this. First was that I had the idea that I might re-use the display for other things in the future. Second was that when all you have is hammer, everything looks like a nail. I’m a software engineer by trade, so my first thought is always to use a programmable microcontroller to solve a problem. I’m so bad that if I needed a square wave, I’d more likely use an 8 pin microcontroller than a 555 chip.

Anyway, when I had my clock’s printed circuit boards made, I had them make several. Now, I’ve added a USB port to one of them, connected it to my PC, and written a program in C# to control it. It can fetch data from local files or the web, extract specific pieces of data, format them and display them on the LEDs. The user can enter C# expressions that evaluate to true or false and cause the discrete LEDs to light up (and even flash). The user can also configure alarm sounds and actions to take when the front panel buttons are pressed.
I’m making my schematic, board layout, and software available for free here. The UI is definitely for techies only, but it could probably be adapted to other PC-controlled displays like those from Crystalfontz and Matrix Orbital.
Here’s a short introduction to the display’s capabilities and UI (if you’re wondering what the computer is in the background, it’s a modern PC in a small form-factor Altair 8800 replica case.

And if you’re considering downloading and playing with the UI, here’s a much more detailed description of it
Finally, here’s the schematic and layout (readable by the open source program Kicad), the PIC 18F4550 firmware (readable by Microchip’s MPLAB and using their free C18 compiler), and the PC UI (readable by Microsoft’s free Visual C# Express):

SCHEMATICS:

DOWNLOADS: