Design and Development of Wireless Home Automation System with Mobile Web Interface Integration

The assignment has two parts;

Part one is the design and development of a portable wireless home automation system. The system requirements are -

Device 1 is a remote control device. It can be used with serial monitor on a host PC, but higher marks will be given to those who use the LCD screen. (portable)

Device 2 is outside the house. It controls the outside light (turning it on automatically when the sun goes down and off when the sun comes up). It also controls the gates with a servo.

Device 3 controls the interior light. The room has a simple (on/off) but also a dimmer function, meaning that the light level can be altered.

Device 4 passive fire detection (infra-red). Detection is from one single source.

All instructions are sent from the remote control. BUT whenever there is a state change at one of the other devices, the remote control is informed.

Any other design decisions are yours to make.

Part two is the integration of a mobile web/App interface with the system designed and created in part 1.

Apply what you have learned on the module to design, implement and document the system as a whole.

Documentation should include assumptions, research into relevant toppics to inform your design decisions, final design by way of a flow diagram or similar, critical evaluation of design and implementation process as well as ideas for expansion of the system.

Report Structure:

An individual technical report detailing the design, implementation and testing of the system is required from each student. The report must include the following (but may include other information as well).

A report should allow the reader to replicate your design and implementation exactly. It should be written in the past-passive tense (‘The LEDs were placed in the printed circuit board’, there is no ‘I’, ‘We’, ‘He’ or ‘They’). It is written in the past tense, because it describes what has already happened.

A report should contain the following:

1.Abstract and Introduction.

An abstract is often written after the rest of the report (although it is submitted at the very front of the report and is the first thing read). It provides a paragraph or two that summarise the contents, results and conclusions of the report that follows. An introduction explains the rationale behind the project and outlines the problem.

2.Aim(s) and Objectives.

Briefly, the aim explains the desired final outcome of the project. Each objective outlines a step that must be undertaken to reach the aim.

3.Research.

Sometimes this takes the form of a literature review, looking at what has been accomplished in related areas. Research also covers the support for design decisions and assumptions and the location of any information that aided the project. For instance, if you were asked to return a haptic output from your arduino, what would you use? You’d need to investigate what ‘haptic’ meant first. You’d have to reference the information you found in the document. You’d then have to investigate available methods, what other people had used and how. You’d be expected to reference this material too, with a brief discussion. You’d then be expected to make a decision on what haptic feedback to use and justify why it was the most suitable for your project. The University expects Harvard referencing.

4.Project Design and Method.

In this module, we deal with the interface between hardware and software. Therefore, your design and method should include the design of the hardware (including how it was arrived at, why it is suitable, what it is intended to accomplish), software (flow diagrams for software design, how variables map to devices, what inputs are expected etc) and the interaction between the two.

5.Implementation.

A description of which elements of your project you successfully completed, issues you overcame successfully and issues you were not able to overcome. Describe each part of your code (simply edit the comments you included in your software into something that makes sense to the reader). Also include any changes that were necessary to your original design that did not become clear until you were at the implementation stage. Include your particular circuit design, indicating which pins on the Arduino were used, for what and what variables they mapped to. Your code should be included as an appendix.

6.Critical evaluation.

Discuss how successful your project was, what you would have done differently and which parts you are particularly happy with. Be honest.

Word count 3000 words