27-04-2011, 03:39 PM
[attachment=12951]
DESCRIPTION OF THE PROJECT
1.1. INTRODUCTION
In this chapter introduction of the PATIENT MONITORING USING GSM AND ZIGBEE FOR HOSPITALS AND OLD AGE HOMES are discussed. It gives overall view of the project design and the related literature and the environment to be considered. Chapter wise organization of the thesis and the appendices is given at the end of this chapter. At first we discuss what the main processing done using 8051 microcontroller is and then what is the process that can be automated which is within the scope of the work. Then we discuss the implementation aspects.
1.2. OVERVIEW
In case of emergency and dangerous situations we have to alert the doctor immediately. For this we are using a Zigbee based network for doctor to patient communication in the hospital and even to communicate and indicate the status of the patient through SMS. This way of communication is actually done with Zigbee network topology and with the GSM network. Each patient will be given this module and with the help of this module the patient health condition is monitored and if there is any change in the condition of the heath then it immediately sends that changed data through Zigbee to the local system where the main module is connected to the computer to maintain the status of the patient.
The heart beat is monitored with the pulse rate of the body. The high intensity light sensor senses the expansion and contraction of the heart with the help of the nerves. That beam will transmit the signal to the receiver and the minuet change in the pulse is noticed as the heart beat. If there is any change in the pulses then it is noticed as the change in the heart and then the controller will get a disturbed pulse count which indicates the fault or malfunction of the heart. The controller is fixed for a no. of pulses initially. If there is any change in the any of the pulse count then it considers as a malfunction of the heart and then it transmits the pulse count with the patients ID to the doctor in the hospital and at the same to it sends a sms to a fixed number in the microcontroller. This is convenient process to monitor the patients health conditions form any of the distance we present. Since we are using both the networks like Zigbee and GSM this makes the user to communicate for internal system and as well as to the longer distances.
1.3. AIM OF THE PROJECT
The main processes involved in this type of control system are to monitor the patient’s health status. Zigbee is a wireless connection network that is used to connect different devices at a frequency of 2.4GHz. For medical applications also this Zigbee is widely used. The Zigbee can communicate with the devices of about 1km. The other network is GSM network. This can be operated from any distance to any point of control. The communication is done with the help of local network support. This can get communicated to any part of the world which the network of the local system is applicable. Here we are using for the hospital communication for monitoring the patient.
1.4. LITERATURE SURVEY
The technical brilliance and development in different fields has led to a drastic in our lives, one among them is embedded systems. The application of these devices is to monitor the patient health status. Zigbee is a wireless connection network that is used to connect different devices at a frequency of 2.4GHz. For medical applications also this Zigbee is widely used. The Zigbee can communicate with the devices of about 1km. The other network is GSM network. This can be operated from any distance to any point of control. The communication is done with the help of local network support. This can get communicated to any part of the world which the network of the local system is applicable. Here we are using for the hospital communication for monitoring the patient.
1.5. ORGANIZATION OF THE THESIS
Chapter 2: Detailed system description and development environment
This chapter gives a brief explanation of the overall design processing and detailed functionality of the circuit and also covers the literature survey i.e. general introduction and features of the hardware elements involved.
Chapter 3: Design Elements
This chapter describes the complete design elements of the project for the microcontroller along with GSM Modem, Zigbee module, sensors and Liquid Crystal Display..
SYSTEM ENVIRONMENT
2.1. INTRODUCTION
The flat form for this project mobile based street light control system is an Embedded System. An Embedded system is a special-purpose system in which the computer is completely encapsulated by the device it controls. Unlike a general-purpose computer, such as a personal computer, an embedded system performs one or a few pre-defined tasks, usually with very specific requirements. Since the system is dedicated to specific tasks, design engineers can optimize it, reducing the size and cost of the product. Embedded systems are often mass-produced, so the cost savings may be multiplied by millions of items.
An embedded system is a special-purpose computer system designed to perform a dedicated function. Unlike a general-purpose computer, such as a personal computer, an embedded system performs one or a few pre-defined tasks, usually with very specific requirements. Since the system is dedicated to specific tasks, design engineers can optimize it, reducing the size and cost of the product. Embedded system comprises of both hardware and software. Embedded system is fast growing technology in various fields like industrial automation, home appliances, automobiles, aeronautics etc. Embedded technology is implemented to perform a specified task and the programming is done using assembly language programming or embedded C. Ours being a developing country the power consumption is increasing on large scale to meet the growing need of the people. Power generation is widely based on the non-renewable sources and these sources being depleting some means have to be found for power saving.
2.2. DESIGN OF EMBEDDED SYSTEMS
Intelligent, programmable and computing electronic device designed to perform specific tasks based on a fixed time frame. An embedded system is a combination of hardware and software, perhaps with some mechanical and other components designed to perform a specific task. The
Fig2.1. Embedded System Design.
electronics usually uses either a microprocessor or a microcontroller. Some large or old systems use general-purpose mainframes computers or minicomputers.
START-UP:
All embedded systems have start-up code. Usually it disables interrupts, sets up the electronics, tests the computer (RAM, CPU and software), and then starts the application code. Many embedded systems recover from short-term power failures by restarting (without recent self-tests). Restart times under a tenth of a second are common.
Many designers have found one of more hardware plus software-controlled LED’s useful to indicate errors during development (and in some instances, after product release, to produce troubleshooting diagnostics). A common scheme is to have the electronics turn off the LED(s) at reset, whereupon the software turns it on at the first opportunity, to prove that the hardware and start-up software have performed their job so far. After that, the software blinks the LED(s) or sets up light patterns during normal operation, to indicate program execution progress and/or errors. This serves to reassure most technicians/engineers and some users.
THE CONTROL LOOP: In this design, the software has a loop. The loop calls subroutines. Each subroutine manages a part of the hardware or software. Interrupts generally set flags, or update counters that are read by the rest of the software. A simple API disables and enables interrupts. Done right, it handles nested calls in nested subroutines, and restores the preceding interrupt state in the outermost enable. This is one of the simplest methods of creating an exocrine.
Typically, there's some sort of subroutine in the loop to manage a list of software timers, using a periodic real time interrupt. When a timer expires, an associated subroutine is run, or flag is set. Any expected hardware event should be backed-up with a software timer. Hardware events fail about once in a trillion times. State machines may be implemented with a function-pointer per state-machine (in C++, C or assembly, anyway). A change of state stores a different function into the pointer. The function pointer is executed every time the loop runs.
Many designers recommend reading each IO device once per loop, and storing the result so the logic acts on consistent values. Many designers prefer to design their state machines to check only one or two things per state. Usually this is a hardware event, and a software timer. Designers recommend that hierarchical state machines should run the lower-level state machines before the higher, so the higher run with accurate information.
Complex functions like internal combustion controls are often handled with multi-dimensional tables. Instead of complex calculations, the code looks up the values. The software can interpolate between entries, to keep the tables small and cheap.
One major disadvantage of this system is that it does not guarantee a time to respond to any particular hardware event. Careful coding can easily assure that nothing disables interrupts for long. Thus interrupt code can run at very precise timings. Another major weakness of this system is that it can become complex to add new features. Algorithms that take a long time to run must be carefully broken down so only a little piece gets done each time through the main loop.
This system's strength is its simplicity, and on small pieces of software the loop is usually so fast that nobody cares that it is not predictable. Another advantage is that this system guarantees that the software will run. There is no mysterious operating system to blame for bad behavior.
USER INTERFACES:
Interface designers at PARC, Apple Computer, Boeing and HP minimize the number of types of user actions. For example, use two buttons (the absolute minimum) to control a menu system (just to be clear, one button should be "next menu entry" the other button should be "select this menu entry"). A touch-screen or screen-edge buttons also minimize the types of user actions.
Another basic trick is to minimize and simplify the type of output. Designs should consider using a status light for each interface plug, or failure condition, to tell what failed. A cheap variation is to have two light bars with a printed matrix of errors that they select- the user can glue on the labels for the language that she speaks.
For example, Boeing's standard test interface is a button and some lights. When you press the button, all the lights turn on. When you release the button, the lights with failures stay on. The labels are in Basic English.
Designers use colors. Red defines the users can get hurt- think of blood. Yellow defines something might be wrong. Green defines everything's OK.
Another essential trick is to make any modes absolutely clear on the user's display. If an interface has modes, they must be reversible in an obvious way. Most designers prefer the display to respond to the user. The display should change immediately after a user action. If the machine is going to do anything, it should start within 7 seconds, or give progress report. One of the most successful general-purpose screen-based interfaces is the two menu buttons and a line of text in the user's native language. It's used in pagers, medium-priced printers, network switches, and other medium-priced situations that require complex behavior from users. When there's text, there are languages. The default language should be the one most widely understood.
