BRISKODA.net: Robshaw - Viewing Profile - BRISKODA.net

http://qkme.me/35ysxk

Enough said....

That's bad....

I would be happy with around £4,000 :thumbup:

I'm sorry that I haven't had a chance to update this further. I'm planning to update the blog with more 'indepth' information but I'm currently having a nightmare here waiting for some equipment to arrive for the hardware side.

The first update is I managed to get myself some Tenvis WI-FI IP Cameras. These come with the following included - Pan/tilt function/ Day and Night vision/ HQ video/ Alarms/ Snapshot pictures/ Recording both video + Audio/ Mobile compatible. Including some brief pictures below - Interesting how in 'night mode' the lights to the human eye are red however below on a camera they are white:

http://i2.photobucket.com/albums/y5/Yodawormtail/IMAG0341.jpg

http://i2.photobucket.com/albums/y5/Yodawormtail/IMAG0340.jpg

Picture quality isn't bad and 'Motion Sensors' picking up the following in pictures and video:

(This also shows the Admin interface panel - so it's easy to setup and configure the cameras).
http://i2.photobucket.com/albums/y5/Yodawormtail/p1.jpg

(This is my housemate finding one) - Video... Click me.
http://i2.photobucket.com/albums/y5/Yodawormtail/th_IPCamera_20120208162111.jpg

I'm going to be honest, I heard that Tenvis was a rip-off of another brand. I'm trying to limit the £££'s spent on this project so this is why I initally went with Tenvis products. I didn't have many issues with these apart from the initial install download that Tenvis provided. I ended up having to find a different install package and wing it from there after spending over an hour on Skype to Tenvis customer support!

The main point to note is to install these as 'wired' devices using an Ethernet cable direct to the router. Then once done - configure it via the admin panel as a wireless setup and remove the Ethernet Cable. I also did a rookie mistake in clicking 'Obtain IP Address from DHCP Server' this rendering the camera useless untill I re-installed the software.

I also got some more hardware to scatter across the house on various different devices. Nothing outstanding to mention here - Just plug and play once I have done the coding side of things. I'm still waiting on alot more to arrive and plan to create a map/floor plan to demonstrate where all the devices are located across the house.

http://i2.photobucket.com/albums/y5/Yodawormtail/IMAG0342.jpg

I had fantastic issues with Bottle Rocket/Rocket Launcher on my test VM. Apparently as I installed the version with the interface the old faithful server has major issues! I would send the command to turn on a light and 10mins later, it would eventually turn on. So, I'm currently installing a text version called HEYU which also works with X10 devices. In talking with my project supervisor my project had too much scope and I was advised to use an Open Source mobile phone application instead of coding my own. I have also been testing a few this week with 'domus' being my number 1 for Android platform which is basically just a 'Front End' for HEYU. More information can be found here: http://domus.link.co.pt/

I also failed to mention that I will be using some Perl. I have been looking here: http://misterhouse.sourceforge.net/ and then good old 'How hard could it be' was said. I plan to link this with my head and arduino chip set for more functionality. (Once it arrives) :dull:

That's all the interesting information out the way. Apparently, I have to do a write up also - Pah. :rofl:. I'm technically 'dyslexic'. I have never let this be an issue or an excuse and will never let this get in my way. The first step to make the write up easier was to split this into sections. I created a 'mind map' from the marking scheme and then applied it to my project making relevant sections:

1. Abstract

2. Project Introduction - Complete
2.1. Project Overview - Complete
2.2. Aims and Objectives - Complete
2.3. Project Scope /Methodology

3. Home Automation System and Technology Research
3.1. Avatar and Graphical User Interfaces Technology Research
3.1.1. Android Mobile Phone Application Research
3.1.2. Conclusions
3.2. Speech Recognition
3.2.1. Speech Recognition Process
3.2.2. Speech Recognition Conclusions
3.3. Speech Synthesis
3.3.1. Speech Synthesiser Conclusions

4. Requirements Elicitation

5. Requirements Specification - Complete
5.1. Functional Requirements - Complete
5.2. Non-Functional Requirements - Complete
5.3. Assumptions

6. Design
6.1. Conversation Controller - Decision Tree
6.1.1. Nodes - Complete
6.1.2. Node Traversal
6.1.3. Decision Tree Traversal
6.1.4. Initiating Conversation from Sleep State
6.2. System UML Activity Diagram
6.3. Speech Recogniser and Speech Synthesiser
6.3.1. Speech Recogniser
6.3.2. Speech Synthesiser
6.3.3. Graphical User Interfaces
6.4. Configuration Manager GUI
6.5. Potential Implementation Issues Analysis

7. Implementation
7.1. Software and Hardware Specification
7.2. Development Methodology
7.3. Avatar
7.3.1. Graphical User Interface and Implementation
7.4. Speech Recogniser
7.4.1. Speech Recognition Implementation Process Overview
7.4.2. XML Configuration and Implementation Detail
7.5. Node and Responses
7.6. Configuration Manager
7.7. Component Integration - Conversation Controller
7.7.1 Additional Integration - Technical Difficulties

8. Testing and Results
8.1. Test Strategy
8.2. Dynamic Black and White Box Testing
8.2.1. Avatar Unit Testing
8.2.2. Speech Recogniser Unit Testing
8.2.3. Mobile Phone Application Testing
8.2.4. Integration Testing
8.2.5. Static Testing

9. Summary, Conclusion and Critique
9.1. Initial Aims and Objectives Assessment
9.1.1 Assessment Conclusion
9.2. Future System Improvements/Enhancements
9.3. Project Management and Development Method Critique (Critical Evaluation)

10. References and Bibliography

11. Appendix
11.1. System Prototype
11.2. User Manual
11.3. Testing
11.4. Dynamic Black Box and White Box Testing
11.5. System Code

I'm probably not going to post every section up (unless you want me to) just so that I don't send everyone on Briskoda to sleep. Today I have been thinking about Nodes and managed to draft up this quick diagram to demonstrate the interaction between the head/user and home network. I plan to redo this using Visio to make it look pretty but it gives you an idea of the thought process as seen simplified below:

Input > Processing > Output

Question/Command > NLP (National Language Processing) > Answer/Action.

http://i2.photobucket.com/albums/y5/Yodawormtail/Node.jpg

Open to thoughts, questions and suggestions - Good or Bad as always. :thumbup:

missingmyvrs, on 08 February 2012 - 14:15, said:

Interesting :thumbup: :smirk: