Mobile Phone Operated Robot
Chapter 1
Abstract of Mobile Phone Operated Robot
BRIEF DESCRIPTION:
The main objective of the project is to design and develop the Mobile Robot that is used to move using wireless system that is controlled by cell phone. Besides that, the goals that want to achieve are: i. To design electronic system for the robots movement and application ii. To implement the relationship between the software and hardware
1.2 Scopes of Project
The generic purpose of Mobile Operated Robot delineated in this project can be further improved to have specific purposes. For a Mobile Operated Robot we need to have 4 controls to roam around. The remaining 8 controls can be configured for other purposes, by some modifications in the software code of microcontroller .For Ex.: It can be used as a Sumo Robot which can fight or defend itself, it can be used as a racer robot, also can be used as video robot to keep a watch on houses,offices,etc. from theft as it can move around in the range of GSM card.
1.2.1 Software Section The Program Embedded C is used for I/O programming in 8051 along with KEIL uvision which is a C compiler used for coding microcontroller.
1.2.2 Hardware Section To build the transmitter and receiver circuit for wireless communication between Mobile and robot. To build the relay circuits to enable DC motor to operate after receiving the signal from receiver. To build the control motor circuit for control the dc motor perfectly (robots movement).
Mobile Phone Operated Robot
1.3 Block Diagram:
Fig 1.1
1.4 Working:
Wireless robot will be controlled by mobile phone. One mobile or GSM modem will be connected to C which is attached to robot. Another will be user mobile. The GSM modem or mobile connected to C board will receive call from user & then user will be able to control the robot. Robot can be operated by following instructions.
KEYS 1 2 3 4 0 ACTION Robot will move forward. Robot will move backward. Robot will move left. Robot will move right. Robot will stop.
Mobile Phone Operated Robot
1.5 Hardware:
Microcontroller AT89C51 GSM Modem.
1.6 Software:
Kiel uv3 (Embedded c)
Conclusion: Thus we have studied the introduction of the project.
Chapter 2
Mobile Phone Operated Robot
Problem Definition and scope of the project
2.1 Problem statement:
Even the Robot can function to do any work as ordered by its brain. The robot operates using stepper motors while allowing it to faster to the left, right, forward and reverse, rotate 360 degree. Its easier to be used especially to carry the goods but can which have a certain limit of carrying. The idea of it came after seeing the difficulties of human being whom have to wipe out the energy and time by doing ordinary works such as carrying, unloading, or transferring goods. Here the ideal thought of producing something which can replace all those works to save energy and time. The project is divided into 2 modules namely Mobile phone & Robot.
2.1.1 Mobile Phone:
There are two mobiles phones to be used in the project. Each of the mobile phone should be supported by GSM modem i.e. it should have GSM sim cards. Out of the two mobiles one will be the user mobile used by the user and the other will be the robot mobile which will be attached to the robot.
2.1.2 Robot:
The robot consists of two main parts:1. DC motor. 2. Electronic circuit.
2.1.3 DC Motor:
There are two DC motors used in our robot so as to move the robot in all directions. Each DC motor should be of 12V, 45 rpm.
2.1.4. Electronic circuit:
The electronic circuit consists of DTMF decoder-CM8870, 8051 microcontroller and a L293D motor driver, all connected on a bread board.
2.2 Scope
Mobile Phone Operated Robot
The generic purpose of Mobile Operated Robot delineated in this project can be further improved to have specific purposes. For a Mobile Operated Robot we need to have 4 controls to roam around. The remaining 8 controls can be configured for other purposes, by some modifications in the software code of microcontroller. For Ex.: It can be used as a Sumo Robot which can fight or defend itself, it can be used as a racer robot, also can be used as video robot to keep a watch on houses,offices,etc. from theft as it can move around in the range of GSM card.
2.3 General Section
2.3.1 Software Section
The Program Embedded C is used for I/O programming in 8051 along with KEIL uvision which is a C compiler used for coding microcontroller.
2.3.2 Hardware Section
To build the transmitter and receiver circuit for wireless communication between Mobile and robot. To build the relay circuits to enable DC motor to operate after receiving the Signal from receiver. To build the control motor circuit for control the dc motor perfectly (robots Movement).
2.3.3 Communication Interface
The communication interfaces include mobile phones with GSM cards, the bread board containing DTMF decoder, microcontroller chip and the motor driver.
2.3.5 Assumptions
The network of the service provider will always be maximum.
2.3.6 Dependencies
Mobile Phone Operated Robot
Full working of the robot is dependent on the availability of network of the service provider.
CONCLUSION:
Thus we studied the scope and problem definition of the project.
Mobile Phone Operated Robot
Chapter 3
Review of Literature
3.1 OBJECTIVE:
Deeper understanding of system modeling Data model: entity relationship diagram(ERD) Functional model: data flow diagram
3.2 OUTLINE
3.2.1 SYSTEM ANALYSIS MODEL ELEMENTS:
Data model: entity relationship diagram(ERD) Functional model: data flow diagram
3.2.2 WHY MODEL SOFTWARE?
Software is getting larger, not smaller. For example, windows XP have more than 40 million lines of code. a single programmer cannot manage this amount of code in its entirety. Code is often not directly understandable by developers who did not participate in the development thus we need simpler representation for complex systems. A wide variety of models have been in use within various engineering disciplines for along time. in software engineering a number of modeling methods are also available.
3.2.3ANALYSIS MODEL OBJECTIVES:
To describe What the customer required To established a basis for the creation of a s/w design To define a set of requirements that can be validated once the s/w is build
Mobile Phone Operated Robot
3.2.4THE GENERIC ANALYSIS MODEL CONSIST OF : 1. ER diagram 2. DFD 3. State transition diagram
3.3ENTITY RELATIONSHIP DIAGRAM
An ER diagram is one means of representing the object ad their relationship in data model for as/w product.
3.3.1NOTATIONS;
Define object by underlining all nouns in the written stmt of scope: Producers/consumers of data, places here data are stored and the composite data items. Define operations by double underling all active verbs :processes relevant to the application and data transformations Consider other services that will be required by the objects. The you need to define the relationship which indicates connectedness
3.3.2DATA FLOW DIAGRAM
A data flow diagram one means of representing the functional model of a s/w product.DFD does not represent program logic like low chart do.
3.3.3NOTATIONS:
Entity Relationship External Entity Process Data flow Control flow Data store
Mobile Phone Operated Robot
3.3.4TO CREATE DATA FLOW DIAGRAM YOU NEED TO:
Review ERD to isolate data objects and grammatical parse to determine operations Determine external entities Create a level 0 DFD context diagram Place the flow to maintain dataflow continuity Develop a level 1 DFD
3.4DATA FLOW DIAGRAM GUIDELINES:
All icons must be labeled with meaningful names. Always show external entities at level 0 Always label at flow arrows Do not represent procedural logic. Each double is refined until it does just one thing.
Conclusion:
Thus we have Reviewed the Literature of the project.
Mobile Phone Operated Robot
Chapter 4
Existing System
4.1PROCESS:
The model employed for the development of MOBILE OPERATED ROBOT.
4.1.1 THE WATERFALL MODEL:
10
Mobile Phone Operated Robot
Fig 4.1 Waterfall Model
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance. The unmodified "waterfall model". Progress flows from the top to the bottom, like a waterfall. The waterfall development model has its origins in the manufacturing and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development. AS PER THE ABOVE MODEL THE PROJECT IS AS FOLLOWS:
4.1.2REQUIREMENTS:
-SOFTWARE. KIEL uv3 (Embedded c) EAGLE
-HARDWARE Microcontroller AT89C51 MAX 232 for PC and Microcontroller interface GSM Modem.
4.1.3ANALYSIS:
-SOFTWARE. KIEL uv3 (Embedded c) : Used for coding of microcontroller. EAGLE: Used for burning of microcontroller.
11
Mobile Phone Operated Robot
-HARDWARE. 8051 microcontroller: Four 8-bit ports. DTMF Decoder: CM8870- CMOS Integrated DTMF Receiver. CM8870C is fully compatible with CM8870 for 18-pin Devices by grounding pins 5 and 6. L293D motor driver: L293D is a PUSH-PULL FOUR CHANNEL DRIVER WITH DIODES. Two mobiles with two GSM sim cards.
12
Mobile Phone Operated Robot
4.1.3DESIGN:
Fig.4.2 Schematic Representation
[2]
13
Mobile Phone Operated Robot
Fig4.3 DTMF TABLE
[2]
4.2TESTING:
The testing is performed on the system to determine its accuracy.
4.3MAINTENANCE:
The maintenance of the system depends upon user. The user should always be aware of the circuits maintenance
4.4 W5HH PRINCIPAL:
Why is the system being developed? In order to represent the robotic technology in the field of wireless communication for unlimited range. In the present age of robotic-technology, it is very necessary to develop some or the other technology that makes the maximum use of robot to help people do their work in an efficient way in their day to day life
14
Mobile Phone Operated Robot
What will be done, by when? Acquiring the resources.: 10-12 days (approx.) Assembling of the resources.: 4-6 days (approx.) Code generation, modification, reuse.: 45-60 days (approx.) Testing.: 7-10 days (approx.)
Who is responsible for a function? As aforementioned, all the team members are collectively putting an effort in all the possible aspects of this venture. Where they are organizationally located? As stated earlier, the customer, the user, and the developer all form a part of the team working on this project. How will the job be done technically and managerially?
4.5 Technically:
8051 microcontroller. DTMF Decoder-CM8870. L293D motor driver. Two mobiles with two GSM sim cards
15
Mobile Phone Operated Robot
How much of each resource is needed? Requirement Mobile phones GSM sim card DC motor DTMF decoder 8051 microcontroller L293D motor driver Breadboard Spare Wires Estimated Quantity 2 2 2 1 1 1 1 m.
Conclusion:
Thus we had an overview of the existing systems.
16
Mobile Phone Operated Robot
Chapter 5
Preliminary Design
5.1SOFTWARE DEVELOPMENT METHODS
UML is not a development method by itself, however, it was designed to be compatible with the leading object-oriented software development methods of its time (for example OMT, Booch method, Objector). Since UML has evolved, some of these methods have been recast to take advantage of the new notations (for example OMT), and new methods have been created based on UML. The best known is IBM Rational Unified Process (RUP). There are many other UML-based methods like Abstraction Method, Dynamic Systems Development Method, and others, designed to provide more specific solutions, or achieve different objectives.
5.2MODELING
It is very important to diagrams of a system. system's model. The documentation such as diagrams. distinguish between the UML model and the set of A diagram is a partial graphical representation of a model also contains a "semantic backplane" written use cases that drive the model elements and
UML diagrams represent two different views of a system model:
Static (or structural) view: Emphasizes the static structure of the system using objects, attributes, operations and relationships. The structural view includes class diagrams and composite structure diagrams. Dynamic (or behavioral) view: Emphasizes the dynamic behavior of the system by showing collaborations among objects and changes to the internal states of objects. This view includes sequence diagrams, activity diagrams and state machine diagrams.
UML models can be exchanged among UML tools by using the XMI interchange format.
17
Mobile Phone Operated Robot
OUTLINE
Visual modeling.
5.3 PROBLEM STATEMENT:
Even the Robot can function to do any work as ordered by its brain. The robot operates using stepper motors while allowing it to faster to the left, right, forward and reverse, rotate 360 degree. Its easier to be used especially to carry the goods but can which have a certain limit of carrying. The idea of it came after seeing the difficulties of human being whom have to wipe Out the energy and time by doing ordinary works such as carrying, unloading, or Transferring goods. Here the ideal thought of producing something which can replace all those works to save energy and time.
AFTER READING THE ABOVE PROBLEM STATEMENT, FIND:
1. Actors 2. Use cases with each actor 3. Find extends or uses use cases (if applicable) 4. Finally: draw the main use case diagram
18
Mobile Phone Operated Robot
5.4 USE CASE DIAGRAM
The behavior of the system under development (i.e. what functionality must be provided by the system) is documented in a use case model that illustrates the system's intended functions (use cases), its surroundings (actors), and relationships between the use cases and actors (use case diagrams).
fig 5.1 Use Case Diagram
19
Mobile Phone Operated Robot
5.5 Activity Diagram
Activity diagram is used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule. Activity diagram is a dynamic diagram which shows the activity and the event that causes the object to be in the particular state.
User Mobile
Robot
Make a call
Receives a call
Gives input
No
Valid input
No operation
Yes
Do the required action
Disconnect the call
Activity Diagram for Mobile Phone Operated Robot
Fig no 5.2 Activity Diagram
20
Mobile Phone Operated Robot
5.4.2 Sequence Diagram:
The sequence diagram shows the pattern of interaction among the object emphasizing the sequencing of message. Sequence Diagram is an easy and intuitive way of describing the behaviors of a system by viewing the interaction between system and environment. Sequence diagram describe interaction among classes in terms of an exchange of message over time. It is made of object and message.
M o b i le p h o n e D T M F d e c o d e r : U ser
89c51
: R obot M a k e s a c a ll
E n c o d e d s ig n a l
D e c o d e d s ig n a l C o m m a n d to ro b o t P e r fo r m s t h e a c t i o n
Fig no 5.2 Sequence diagram
21
Mobile Phone Operated Robot
5.4.3 Collaboration diagram
This is another type interaction diagram. A collaboration diagram represents a collaboration, which is a set of object related in particular context and interaction, which is set of message exchanged among the object while the collaboration to achieve a desire outcome. In the collaboration diagram, objects are shown as figures. As in the sequence diagram, arrows indicate the message sent within the use case.
2: Encoded signal Mobile phone DTMF decoder
3: Decoded signal 89c51
1: Makes a call
4: Command to robot 5: Performs the action
: User
: Robot
Fig no 5.3 Collaboration Diagram
22
Mobile Phone Operated Robot
Conclusion: Thus we completed with the preliminary design of
the project
Chapter 6
Requirement Analysis
6.1 Software Section
The Program Embedded C is used for I/O programming in 8051 along with KEIL uvision which is a C compiler used for coding microcontroller.
6.2 Hardware Section
To build the transmitter and receiver circuit for wireless communication between Mobile and robot. To build the relay circuits to enable DC motor to operate after receiving the Signal from receiver. To build the control motor circuit for control the dc motor perfectly (robots Movement).
6.3 Communication Interface
The communication interfaces include mobile phones with GSM cards, the bread board containing DTMF decoder, microcontroller chip and the motor driver.
6.4 Assumptions
The network of the service provider will always be maximum.
6.5 Dependencies
Full working of the robot is dependent on the availability of network of the service provider.
6.6 Integrity
23
Mobile Phone Operated Robot
The design shall provide the capability to generate more actions based on future requirements of the robot.
6.7 ORGANIZING REQUIREMENTS
Features:
Convenient Expandable Supports modularity Easy maintenance Easily portable High reusability
THE
SPECIFIC
Conclusion: Thus we studied the requirement analysis of the
system.
24
Mobile Phone Operated Robot
Chapter 7
Development Tools
7.1 GOLDEN RULES FOR USER INTERFACE DESIGN:Place the user in control. 1. 2. Reduce the users memory load. Make the interface consistent.
These golden rules actually form the basis for a set of user interface design principles that guide this important software design activity.
7.2TASK ANALYSIS AND MODELLING:
The most important thing about the undertaken endeavor is that the major part of it consists of Software, thereby differentiating itself in terms of steps to be taken for task analysis, as compared to other conventional software ventures. Password Management for Personalize network solves this problem by providing a secure system to Store, Administer, and Share passwords. So considering the above defined context, following are the possible major tasks involved while implementing such system. Assembling and Interfacing of the different Modules, and Compilation and Execution of the computational algorithms. Training the network to be precise in its Diagnosis. Only the above mentioned tasks capture the entire implementation as well as the functional view of Password Manager Now the first major task of Assembling and Interfacing, can be further refined into number of diminutive steps as follows: Write different code for three major Decision Making Criterias
25
Mobile Phone Operated Robot
. Plan and implement a precise C4.5 algorithm Also plan a suitable function for feature extraction.
Proper Interfacing between all these different modules. The second major task of Compilation and Execution, can be refined as follows. Supplying Data Sets to the KEIL software. Run the compilation code as the network is trained. Look out for any errors and debug if possible. Execute the entire system again with a new Data Set to produce a flawless result.
7.3INTERFACE DESIGN ACTIVITIES:
For our project, there really is scope and need for a user interface, since all the possible alterations, interactions and actions from the user side, can be handled by the EMBEDDED C.. User interface is absolutely mandatory for the following conditions: When the prerequisites required for the successful execution of the end-product has not been provided by the Operating System. Assuming that the prerequisites are provided by the OS, but it involves access and/or temporary modifications of the system files, which can be detrimental, if not handled properly. Just for the sake of user-friendliness. Since our project does not necessarily fall into the category of those software, which absolutely needs a user interface for a user to interact with it, we will have to consider the itself as the User Interface, and we will proceed with the further interface analysis based on the same.
7.4DEFINING INTERFACE OBJECTS AND ACTIONS:
Following are the various objects falling in the mentioned category Source Object: All the Data Sets provided to the software. Target Object: The KEIL software and its results placed into a text file. Application Object: EMBEDED C used for compilation and execution.
26
Mobile Phone Operated Robot
7.5 DESIGN ISSUES:
Following are some of the Design Issues for devising the user interface: System Response Time: Since there are only few software parts to deal with, the user wont have to wait too long neither will he have to be hasty in his operating of the system. The only thing user will have to anticipate is the final snooped display, which can never go unnoticed, since it will be displayed on an at least, 15 inch monitor. Even if there is a slight delay, then as will be provided in the manual, the only adjustment needs to be done is the hardware. User help facilities: The amount of help manual needed to for the operation of KEIL is very low in terms of volume. Because, each and every piece of hardware and software, would have gone through intensive tests, before it is released officially. Also the hardware desired for the successful operation of the end product will be provided along with the compatible software codes, thereby eliminating the immense dependency on the help-manual.
The system is itself comprised of software which has about only few hundreds of codes, and which again will be tested before the release. And there is no additional piece of syntactical code that needs to be added, for the processing of the product. But as a last resort, a simple text document, though comprehensive and concise would be provided, where all the program related matters would be answered, thus making it an integrated help facility approach. Some other design issues that normally accompanies other conventional products: Help will be available as an all-inclusive and a precise text document, thus making it available all the time, while the product is in use. During the help session, a user can switch back to the original operation, just like any user does while operating any given software.
27
Mobile Phone Operated Robot
7.6 IMPLEMENTATION
TOOLS:
As stated in all the previous analysis, the OS used for the product i.e. Windows, KEIL itself will be acting as a User Interface, due to very little and almost negligible involvement of the product-driven commands or functionality, since the product itself has no need for these customizations. Due to reliance on the user interface, we have gained following advantages for the development of the system. Easy Availability of functions. Specialized tools for the user interface design helps even a lay man to use our product.
So all the required testing can be carried out on the KEIL itself.
7.7DESIGN EVALUATION:
As this is our last year project, we are assuming the role of both, the developer and the end user. Considering the OS and the user interaction required for the operation of the product, following analysis has been made: There will be absolutely nil amount of training required for using the product. The number of user tasks, are just limited to the execution of the single code, which will automatically hierarchically compile all the remaining piece of code. Though the initial interaction would not incur much load on the system, but it is possible that the final output may need somewhat large amount of processing power and memory space, for interrupted execution.
The iterative study and evaluation for the interaction between the final product and the MATLAB will be performed by us, only after the initial trial of the system is carried out. Thus after the meticulous analysis for the user interface design, the only prerequisite required from the end user side is the Acclimatization to the OS & KEIL, which is only needed if the end-user has been following other operating systems, and for such case too, the user manual to get acquainted to the new user will be provided by us.
28
Mobile Phone Operated Robot
Conclusion: Thus we had an overview of the development tools required for mobile phone operated robot.
Chapter 8 Estimation and Planning:
To achieve reliable cost and effort estimates, a number of options arise: 1. Delay estimation until late in the project (obviously, we can achieve 100% accurate estimates after the project is complete!). 2. Base estimates on similar projects that have already been completed. 3. Use relatively simple decomposition techniques to generate project cost and effort estimates. 4. Use one or more empirical models for software cost and effort estimation.
8.1 PROGRAM BASED ESTIMATION:
Lines of code and function points were described as measures from which productivity metrics can be computed. LOC and FP data are used in two ways during software project estimation: (1) as an estimation variable to "size" each element of the software and (2) as baseline metrics collected from past projects and used in conjunction with estimation variables to develop cost and effort projections. LOC and FP estimation are distinct estimation techniques. Yet both have a number of characteristics in common. The project planner begins with a bounded statement of software scope and from this statement attempts to decompose software into problem functions that can each be estimated individually. LOC or FP (the estimation variable) is then estimated for each function. Alternatively, the planner may choose another component for sizing such as classes or objects, changes, or business processes affected.
29
Mobile Phone Operated Robot
Baseline productivity metrics (e.g., LOC/pm or FP/pm9) are then applied to the appropriate estimation variable, and cost or effort for the function is derived. Function estimates are combined to produce an overall estimate for the entire project. It is important to note, however, that there is often substantial scatter in productivity metrics for an organization, making the use of a single baseline productivity metric suspect. In general, LOC/pm or FP/pm averages should be computed by project domain. That is, projects should be grouped by team size, application area, complexity, and other relevant parameters.
8.2 LOC BASED ESTIMATION:
A review of the System Specification indicates that the software is to execute on an engineering workstation and must interface with various computer graphics peripherals including a mouse, high resolution color display and laser printer. For our purposes, we assume that further refinement has occurred and that the following major software functions are identified: User interface and control facilities (UICF) RBFNN Classifier Windowing 3 Decision Making Criterias
Function Windowing RBFNN Classifier Decision criteria 1 Decision criteria 2 Decision criteria 3 Estimated Lines of Code
Estimated LOC 400 100 500 500 500 2000
30
Mobile Phone Operated Robot
8.3 FP-BASED ESTIMATION:
Decomposition for FP-based estimation focuses on information domain values rather than software functions. Referring to the function point calculation table presented in Figure below , the project planner estimates inputs, outputs, inquiries, files, and external interfaces for the CAD software. For the purposes of this estimate, the complexity weighting factor is assumed to be average.
Information Optimum Likely Pessimistic Estimated Weight FP Domain Count Count Value No. Of Inputs No. Of Outputs No. Of Inquiries No. Of Files No. Of External Interface Count Total 25 2 32 4 0 36 20 2 20 4 0 24 35 2 14 4 0 18 27 2 22 4 0 26 4 8 6 3 0 9 90 95 70 65 0 135
Each of the complexity weighting factors is estimated and the complexity adjustment factor is computed:
FACTOR
Backup and recovery
VALUE
4
31
Mobile Phone Operated Robot
Data communications Distributed processing Performance critical Existing operating environment On-line data entry Input transaction over multiple screens Master files updated on-line Information domain values complex Internal processing complex Code designed for reuse Conversion/installation in design Multiple installations Application designed for change Complexity adjustment factor
2 0 4 3 4 5 3 5 5 4 3 5 5 1.17
Finally, the estimated number of FP is derived: Festinated = count-total x [0.65 + 0.01 x _ (Fi)] Festinated = 375 The organizational average productivity for systems of this type is 6.5 FP/pm. Based on a burdened labor rate of $8000 per month; the cost per FP is approximately $1230. Based on the LOC estimate and the historical productivity data, the total estimated project cost is $461,000 and the estimated effort is 58 person-months.
8.4 THE COCOMO MODEL
In his classic book on software engineering economics, Barry Boehm [BOE81] introduced a hierarchy of software estimation models bearing the name COCOMO, for COnstructive COst MOdel. The original COCOMO model became one of the most widely used and discussed software cost estimation models in the industry. It has evolved into a more comprehensive estimation model, called COCOMO II [BOE96, BOE00].
32
Mobile Phone Operated Robot
8.4.1 DETAILED REPORT:
Table no 8.1 Component Detail
8.4.2 ACTIVITY REPORT:
33
Mobile Phone Operated Robot
Table no 8.2 Activity Report
8.4.3. SCHEDULE REPORT:
Table no 8.4 Schedule Report
Conclusion:
Thus we had an overview of the Estimation and Planning required for mobile phone operated robot.
34
Mobile Phone Operated Robot
Chapter 9
Proposed system
9.1 System
In the present project the robot is controlled by a mobile phone which makes a call to the mobile phone attached to the robot. In the course of a call if any button is pressed a tone corresponding to the button pressed is heard at the other end of the call. This tone is called DTMF tone. The robot perceives this DTMF tone with the help of a phone stacked in the robot. The processing of the received tone is done by Atmega 32 microcontroller with the help of DTMF decoder, HT9170. The decoder decodes the DTMF tone in to its equivalent binary digit and this binary number is sent to the microcontroller. The microcontroller is preprogrammed to take a decision for any given input. The microcontroller outputs its decision to motor drivers to drive the motors in order to have forward or backward motion or a turn. Any mobile which makes a call to the mobile phone stacked in the robot will act as remote. So, this is a simple robotic project which even does not require the construction of receiver and transmitter kits, but has an innovated application of cell phone and robust control.
35
Mobile Phone Operated Robot
Fig no 9.1
[4]
9.2Working
The user in order to control the robot should make a call to the cell phone attached in the robot, from any phone, which can send DTMF tunes on pressing the numeric buttons. The cell phone in the robot will be kept in auto answer mode. So, after a ring the cell phone accepts the call. Now the user may press any button on his mobile. The DTMF tones thus produced are received by the cell phone in the robot. These tones are fed to the circuit by head set of the cell phone. HT 9170 decodes the received toneand sends equivalent binary number to the micro controller. According to the program in the microcontroller, the robot starts moving.
Conclusion: Thus we studied the various diagrams for the system.
36
Mobile Phone Operated Robot
Chapter 10
REFERENCES
1. Wikipedia - The free encyclopedia 2. http://www.8051projects.info/ 3. http://www.instructables.com/
37
Mobile Phone Operated Robot
4. Schenker, L (1960), "Pushbutton Calling with a Two-Group Voice-Frequency Code", The Bell system technical journal 39 (1): 235255, ISSN 0005-8580 5. DTMF Tester , Electronics For You Magazine , Edition (June 2003) 6. http://www.alldatasheet.com/ 7. http://www.datasheet4u.com/ 8. http://www.datasheetcatalog.com/
38
