laser-sight lockdown - proj354.comproj354.com/itcs/10to19/2014/f4/docs/hold it down... · web...

Hold it down! industries

Laser-Sight Lockdown

Final Report

Chris Buchanan, Travis Midwinter and Andrew Tyukasz

LASER-SIGHT LOCKDOWN FINAL REPORTPAGE 0

TABLE OF CONTENTS

1. Executive Summary2. Abstract3. Introduction

a. Backgroundb. Terminology

4. Opportunity5. Budget

a. Equipmentb. Operating Costsc. Variances

6. Methoda. Hardware

i. Serverii. Raspberry Piiii. Servoiv. Camerav. Wireless Donglevi. Ninja Blocks Pi Crustvii. USB Hub

viii. Routerix. SD Cardx. Motion Sensorsxi. Softwarexii. Code

xiii. Operating Systems1. Server2. Raspberry Pi3. Miscellaneous

xiv. Casexv. Mounting Brackets

xvi. Battery Packxvii. Wiringxviii. Infrared Sensors

b. Securityi. Windows Server

ii. Raspberry Pic. Services

i. DHCPii. DNSiii. NFS

7. Objectivesa. Results

i. Raspberry Pi1. Camera2. Servo3. Infrared Sensors4. Wireless Dongle

ii. Server 1. DHCP2. DNS3. NFS4. Network

a. Router8. Challenges

a. What did we face? b. How did we overcome it?

9. Further Developmenta. Opportunities with the systemb. Potential recommendations

10. Conclusion11. Appendixes

a. Project Charterb. Gantt Chartc. Change Requestd. Security Strategy e. User / Operator Manuals

i. Serverii. Raspberry Pi

f. Figuresg. Bibliography


1.0 - EXECUTIVE SUMMARY

This project is a fully implementation security system that will be used to lock down a perimeter and give an administrator an outside look at what is going on around a property. This is done by using PIR sensors linked to a Raspberry Pi & Ninja Blocks Pi Crust that will turn on a camera once a positive motion response has been detected. All data compiled from the system will be saved to a NFS share on a local computer (ie., server, desktop, etc.). When a positive motion response has been detected, a camera will take multiple photos, save them to Google Drive, send them as an email to a user’s personal email or even go as far as to calling the user with a perimeter breach. This project is able to be implemented in numerous locations and is almost infinitely scalable to allow for great versatility at a desired budget.

2.0 - ABSTRACT

Our primary goal with this project is to bring an affordable security solution to any enthusiastic consumer who is looking to secure a room without any major financial setbacks. The system is designed to be accessed from the internet thus making the video stream available to most electronic devices on today’s market. Essentially the construction of the device is fairly simple. We use a web camera that is armed with two servo motors to enable panning and tilting of the camera to better follow and capture an intruder’s face. Another subsection of the detection mechanism is the use of a third party board that enables the primary board (raspberry pi) to receive radio signals at 433 MHz from infrared sensors that can be placed opposite each other in the same room. The reason for the infrared sensors is to create another layer of lock on when trying to capture the intruder’s face.

The second half of the infrastructure uses a server to host said video stream for those accounts with sufficient permissions which are looking to view it. This server also is used to host a mini-network which piggy backs on SAIT’s larger network and internet capabilities. Essentially the topography is fairly simple: One small network with a server and a router which will proceed to distribute IP addresses to any device that has the credentials to access our router. The credentials will then give the device access to the internet and access to our NFS share which will be used to host the video stream on our website as well as transfer files between the devices on our micro network via a Wi-Fi network protocol.

2.1 - TWO MAJOR INFRASTRUCTURE COMPONENTS:

1. Server and Network Component Router Server Services

2. Raspberry Pi Component Raspberry Pi Board


o Dongleo Breadboard/Kobblero USB Hubo SD card With Raspbian

Ninja Blocks Pi Crusto *Radio Transceivers

Our project addresses providing a financially viable home security solution that would cater to those who wish to secure a room of their choice without spending the time and funds to implement a major home security install. Some may choose to secure their home with our system while some may choose to pair it with a professional branded system in order to achieve a 360 degree security system covering all points. Young apartment dwellers will most likely be the largest target demographic as our system will not only provide better than exceptional coverage, but it can be running at all hours of the day and is made for small to regular sized rooms.

3.0 - INTRODUCTION

3.1 - BACKGROUND

When considering the real-estate market in Calgary it is very obvious that most people between the ages of eighteen and twenty four will end up residing in apartment buildings until they have enough money saved to potentially buy a house. We were wondering as a group what these people do in terms of personal security, aside from what physical security a landlord is required to provide. What could a young mind do to actually secure their belongings beyond physical security? With financial constraints considered there are very few options available to this demographic. SAIT requires that we complete a capstone project so nailing two birds with one stone just felt natural. As a group we managed to create a project that solves this problem while effectively meeting all capstone requirements. Said requirements include:

Hardware Software Networking 3 functioning server services Effective project management

We have had the opportunity to implement many of the key areas of study into solving the problem at hand thus making it an ideal capstone project. Aside from the list above we implemented a great deal of critical thinking, troubleshooting and collaborating throughout the semester in order to effectively solve the problem at hand.

3.2 - TERMINOLOGY

The concept of Laser Sight Lockdown provides the end user with many acronyms and terms that the average person may not be familiar with. Many of these terms are synonymous with those found in any regular information technology working environment, but some are unique to our specific project.


This portion of the document is dedicated to the end user, hopefully enabling who ever may be interested in utilizing our system to better implement and scale it according to their specific needs.

Raspberry Pi – A credit card sized computer created and designed to aid in the education of computer science majors around the world. [1]

Rasbian – Standard raspberry pi OS, modified version of the wheezy release specifically designed to be coupled with raspberry pi hardware.

Wireless Dongle – Wireless Adapter. [2]

Pi Cobbler – Connector cable connecting the raspberry pi GPI pins to a breadboard or other device for ease of access. (Looks like a ribbon cable)

USB Hub – Universal serial bus hub, adding extra USB ports to any device which requires more than it has.

Ninja Blocks Pi Crust – Another card sized computer board that acts as an Arduino micro controller and 433mhz transceiver built into one. Mounted on top of the pi, this new board was developed to make integration between the raspberry pi architecture and Arduino micro controller architecture easier than it was in the past, while providing radio signal connectivity. [3]

HTML – (Hypertext markup language) A commonly accepted language for writing internet websites to be displayed in a web browser.

Overclocking – overclocking is the process of making a computer’s central processing unit or other component run faster than the clock frequency specified by the manufacturer. [4] This can cause the component to overheat thus needing extra cooling capability to ensure proper functionality for any length of time.

Radio Transceiver – A radio frequency transmitter and receiver housed in one piece of hardware. [5]

Servomotor – Wiki Definition: “A rotary actuator that allows a precise control of angular position, velocity and acceleration. “ [6] A motor that produces torque through modulation of moving gears housed in a single optimized enclosure.

Breadboard – A plastic prototyping board that allows the user to map wiring schemes without any soldering, making it excellent for experimentation.

NFS – (Network file system) Used to transfer files seamlessly over the network using a generally accepted file structure. Developed by sun microsystems in 1988 and is still in use today. [7]

GPIO Pins – (General purpose input output pins) Electronic pins that can be programmed and controlled by the user at runtime to perform tasks within the capabilities of the board they are mounted on. [8]

Companion Board – A chip board that uses a host board’s resources and is connected directly to the host.

4.0 - STATEMENT OF OPPORTUNITY


It’s obvious that there are other security systems available on the market in all sizes and forms, ranging from a one stop install to pay per month. Many of these systems do not enable a large degree of scalability at a lower price point, thus making these models unavailable to small business’ and people with a tight budget. Fortunately for this market demographic we have developed a system that scales easily and can be purchased for a fraction of the cost of competing systems. Another thing to mention is that our system only records when triggers have been set off thus drastically reducing the amount of video feed that the security professional, whoever they may be, will have to sift through. This feature also reduces the overall cost of ownership to the end user as anyone can sit down and watch the recorded video as it will be only recording during times of movement in the secured room.

Requirements to meet this opportunity are as follows:

Laser Sight Lockdown must be scalable. When coupled with a high powered computer or server, the number of raspberry pi camera systems found on any network could be only limited to the amount of space that each would need to store video feed.

Laser Sight Lockdown must be affordable. Assuming the location has some kind of computer to store video feed, the actual system components themselves must be affordable to anyone on a tight budget. The camera’s themselves are far more affordable than most security camera’s not to mention they can be upgraded to better suit the end user’s needs.

Laser Sight Lockdown must be compatible. Due to the vast majority of users running some kind of windows operating system, we have designed the system to be a Linux-Windows hybrid. The Linux component falls to the individual camera nodes thus making a Linux server environment perfect for operation. Due to licensing issues, Macintosh users may have to wait for further software development to achieve full functionality.

5.0 – BUDGET

5.1 – INITIAL PROPOSITIONS

To complete our project a budget of $xxx.xx is required to distribute enough funds to complete the project’s functionality. The budget has taken in account market values of equipment today. We’ve taken all software, hardware, networking equipment and operating costs in consideration while calculating the total cost of the project budget.

Initially the costs were very light as we did not take into account the server we were using for the project.

5.1.1 – EQUIPMENT AND FACILITIESItem Descriptio

nPre-Owned?

Contingency?

Cost

MD213 Facility Yes N/A $0.00Chris’ Apartment Facility Yes N/A $0.00


Travis’ House Facility Yes N/A $0.00Router Equipment Yes Yes $50.0

0Infrared Sensors Equipment No Yes $10Camera Equipment No No $40Cabling Equipment Yes Yes $20Raspberry Pi Equipment No Yes $35.0

0Raspberry Pi Lens Equipment No Yes $7.00Raspberry Pi WiFi Equipment No Yes $8.00Pi Cobbler Equipment No Yes $8.27Breadboard Equipment No Yes $15.0

8TOTAL COST $118.

35

Figure 1

5.1.2 – OPERATING COSTSItem Hours Rate CostElectricity 24 8.9

cents/kWh

$6.52/day

Operator .05 $30.00 $1.50/use

Physical Labor ($80 x Hours)

660 $80.00 $52800

Chris Buchanan Labor

229 $80.00 $18320

Travis Midwinter Labor

211 $80.00 $16880

Andrew Tyukasz Labor

220 $80.00 $17600

TOTAL COST $52957.23

Figure 2

5.2 – FINALIZED REVISIONIn order to implement the project, a total cost of $68,524.95 would be used to build our project. This accounts for labor costs. However, considering the actual hardware and software costs, the price of the project for a business is still relatively low, unless an individual would implement it in their home. In theory, the server can be substituted with any PC, making hardware and software costs reliant on the end user.

5.2.1 – HARDWARE Item Description Cost


Linksys WRT65G Wireless Router $50.00HP Proliant G385 G7 Server

Server Hardware $2760.00

SecurityMan SM-80 Motion Sensor $20.00Microsoft Lifecam VX2000 (1318)

Webcam $20.00

CAT6 cables(3 cables in total used)

Ethernet cables $15.00 (total)

Raspberry Pi Model B 756-8308 Revision 2

Credit card sized computer

$39.81

Ninja Blocks Pi-Crust Companion Board $45.00SD cards Memory Cards $20.00EDUP EP-N8508 NANO-USB

Wireless Network Card

$5.85

HTC Micro USB Data Cable

USB cable $2.99

LG 19” Monitor Computer Monitor $100.00TOTAL COST $3100

Figure 3

5.2.2 – SOFTWARE Item Description CostWindows Server 2012

Server Operating System

$684.95

Raspbian Wheezy Raspberry Pi Operating System

Freeware

TOTAL COST $684.95

Figure 4

5.2.3 - OPERATING COSTSItem Hours Rate CostChris Buchanan

Management 24 $120.00 $2880.00Implementation 229 $85 $19465.00Travis Midwinter

Management 24 $120.00 $2880.00Implementation 220 $85 $18700.00Andrew Tyukasz

Management 24 $120.00 $2880.00Implementation 211 $85 $17935.00


TOTAL COST $64740.00

Figure 5

6.0 - METHOD

6.1 - HARDWARE

As a whole this project has two major hardware components: A server and a micro-computer. The server was used to represent what someone could do in terms of scalability and market place capabilities. The server we decided to use is an industry standard HP G7 Proliant Series but in the end any user could install the drivers and software on a machine that can handle the software’s system requirements. That being said, our system can be ported on to many different platforms thus making it a highly versatile solution both for the market and home use.

The second hardware component, the raspberry pi micro-computer, is used to manage the commands needed to make this security system functional. Due to advances in technology, this little piece of hardware can do magnificent things at a very appealing price point thus making it an option for many different users. Our operating system of choice is the stock Raspbian Linux. The capabilities of this board, and the support community are what make this particular microcomputer ideal for this project.

6.1.1 - SERVER

This computer system is used to store all files except the base drivers and required programs which are needed to create functionality of the recording device on the raspberry pi. That being said the server also provides essential services to the network which in turn make our project considerably more scalable for the addition of more micro-computers, all of which would store their files over the network on the server to eliminate the need for storage on each device.

Manufacturer: Hewlett Packard Model: Proliant G385 G7 Server CPU: 2x AMD Opteron™ Processor 6234 Memory: 16GB HDD: 6 @ 300GB = 1.8 TB


Figure 6

6.1.2 – RASPBERRY PI

The bulk of this project revolves around the effective use of a micro-computer to achieve functionality outside the realm of a typical low cost surveillance system. Thankfully the Raspberry Pi provides this additional functionality at a low price point. We decided to use Raspberry Pi version B with an increased RAM count of 512 MB. The full tech specs are as follows:

Manufacturer: Raspberry Pi Model Revision 2 CPU: Broadcom BCM2835 ARM1176JZFS Processor with FPU and Videocore 4 GPU Memory: 512MB HDD: External SD


Figure 7

6.1.4 – MICROSOFT WEB CAMERA VX2000 (1318)

Essentially most web cameras will work as long as they can take still photos. The web camera chosen is a standard issue base model web cam that one could find in any business or home hardware repository.


Figure 8

6.1.5.1 – WIRELESS DONGLE EDUP EP-N8508 NANO-USB WIRELESS NETWORK CARD

The Raspberry Pi needs to communicate wirelessly to ensure the systems adaptability and portability to any room. To achieve this we decided on buying a wireless dongle from overseas to save money as well as make sure the dongles drivers are Linux compatible. When building the project always consider that the Raspberry Pi is running some kind of Linux distribution and drivers are sometimes only windows

compatible.

Figure 9

6.1.5.2 – WIRELESS DONGLE TP LINK TL-WN722N HIGH GAIN WIRELESS TRANSCEIVER

For larger businesses this dongle will be key in creating a greater range for the system to communicate over.

Figure 10

6.1.6 – NINJA BLOCKS PI CRUST


When looking to achieve micro-controller functionality we initially figured that we could have achieved all the required functionality by using just the base Raspberry Pi. Unfortunately the Raspberry Pi would have needed some additional components to receive radio signals at 433mhz, and the installation of drivers and pin designation. All of these additional steps would create a huge potential for error when trying run the camera drivers, and other required drivers and services. When browsing the web a solution was found in the Ninja Blocks Pi Crust. The device is essentially an Arduino on steroids, armed with 433mhz radio transceiver which doesn’t interfere with any of the GPIO pins provided by the Raspberry Pi. The Arduino board is also fully functional, but unfortunately the device has very little support with regards to the required software due to the fact the technology is still in its infancy.

Figure 11

6.1.7 – USB HUB

For the development of the Raspberry Pi we needed to add additional USB ports for extra peripherals such as a keyboard and mouse.

Figure 12


6.1.8 - LINKSYS WRT54G WIRELESS ROUTER

To establish connection to the network we needed to acquire a solid wireless router which we could use to implement our server services. Said choice stated above was perfect for the tasks at hand, and even performed one of the services on its own right out of the box.

Figure 13

6.1.9 – SD CARDS

Having one or two SD cards during the development phase is critical due to the fact that the Raspberry Pi can error out at any given time for absolutely no reason. That being said it is always a good idea to have some kind of backup available in case something does happen to the software and you need to restore. Another thing to note is that the Raspberry Pi uses SD cards as its only form of storage, therefor making them essential for operation.


Figure 14

6.1.10 – SECURITY MAN SM80 MOTION SENSOR

Having wireless motion detection is another key component of the project as it is the triggering device that starts off code execution. The wireless signal is transferred over 433mhz to the Ninja Blocks Pi Crust which is then sent through the net to the ninja cloud for processing. Essentially if you wanted to lock an entire building down you could have hundreds of these sensors mounted anywhere which will each feed a different message to the end user. That being said, the Ninja Blocks Pi Crust acts as a node to the internet for as many motion sensors as the user feels the need to pair it with.

Figure 15


6.2 SOFTWARE

6.2.1 – CODE

NINJA BLOCKS CLOUD WEBCAM WIDGET EDITING

HTML<span class="camTimestamp" /><a class="play button icon">▶</a><a class="pause button">‖</a><img class="camStream" src='{{streamUri}}/rest/v0/camera/{{ webcamGuid

}}/snapshot'/><div class="errorImage" style="display: none"> <span class="icon">📷</span> <em>No image</em></div>

CSS.camStream { position: relative; top: 30px; width: 100%; z-index: 0;// opacity: 0;}.camTimestamp { position: absolute; bottom: 0px; width: 100%; background: white; text-align: center;}.play { position: absolute; top: 30px; right: 0px; z-index: 1;}.pause { position: absolute; top: 30px; right: 0px; z-index: 1;}.icon { font-family: 'entypo'; font-size: 30px;}.errorImage { position: absolute; top: 15px;


left: 0px; width: 100%; text-align: center; opacity: 1; .icon { line-height: 180px; font-size: 200px; clear: both; display: block; }}

Javascript

var camImage = element.find(".camStream");var errorImage = element.find(".errorImage");var camTimestamp = element.find(".camTimestamp");var play = element.find(".play").show();var pause = element.find(".pause").hide();

var fadeTime = 1000;

var webcamDevice = scope.Widget.devices[_.keys(scope.Widget.devices)[0]];var NinjaCam = scope.GetNinjaDevice(webcamDevice);

// Set Error HandlercamImage.error(function() { console.log("Webcam Error", Environment, camImage); camImage.fadeOut(fadeTime); errorImage.fadeIn(fadeTime); camTimestamp.fadeOut(fadeTime);})

// Assign Image$timeout(function() { camImage.attr("src", Environment.StreamServer + "/rest/v0/camera/" +

NinjaCam.GUID() + "/snapshot");}, 0);

// Play the imagesfunction Play() { console.log("Playing"); var t = new Date(); camImage.load(function() { console.log("Loading");


camTimestamp.text(t.toLocaleTimeString()).fadeIn(fadeTime); this.src = this.src; errorImage.fadeOut(fadeTime); camImage.fadeIn(fadeTime); }).trigger('load'); camImage.src = Environment.StreamServer + "/rest/v0/camera/" +

NinjaCam.GUID() + "/snapshot";

pause.show(); play.hide();}

play.on("click", function(event) { if ((typeof event) !== "undefined") event.preventDefault(); Play();});pause.on("click", function(event) { if ((typeof event) !== "undefined") event.preventDefault(); play.show(); pause.hide(); camImage.off(); camImage.error(function() { console.log("Webcam Error", Environment, camImage); camImage.fadeOut(fadeTime); errorImage.fadeIn(fadeTime); camTimestamp.fadeOut(fadeTime); }) });

scope.onData = function(data) {}

6.2.2 – OPERATING SYSTEMS

Windows Server 2012

Initially we were thinking of going with Windows Server 2008 R2 to avoid any undisclosed issues that may arise with the implementation of a new firmware. Despite the odds, we decided to use Server 2012 to implement storage services, and various server services. No virtual machines were used, all of the services are installed directly onto the bare metal operating system. Such services include: DHCP, DNS, NFS, and we promoted the machine to a domain controller and created a micro network consisting of the server and Raspberry Pi. The server essentially creates an environment that is easily scalable if someone were to add more Raspberry Pi’s to the network.

Linux Raspbian Wheezy

Our Raspberry Pi is currently running the stock operating system that it was shipped with for good reason. Many of the other available releases of Linux that are compatible with the Raspberry Pi serve extremely specific functions and vary in available kernel modules. Initially we were considering using Occidentalis because it came stock with


PWM modules used for servo control. Unfortunately this operating system was lacking certain kernel modules to have a camera functionality so Raspbian was the obvious choice.

6.3 - MISCELLANEOUS

6.3.1 – CASE

Throughout the development of this project we thought long and hard about what we should do for casing. Considering the system is designed to act as a security network, having a tamper proof case was obviously on the mind. Considering the scope of the project, time had come to work against us. Regardless we proceeded to spark an idea that made the creation of the case a breeze while leaving room for expandability and that idea can be found at almost every mall in America, the idea of using Lego as a building material. By using Lego we made a solid case which left enough room to accommodate the camera and all the Raspberry Pi’s peripheral slots, not to mention it can be ripped down to accommodate fan systems and other externals which may enable the pi to continue operation for a long period of time without the need for a reboot. If a small business were to implement this idea, they may want to glue the blocks together and create a permanent door for troubleshooting while keeping intruders out.

6.3.2 – WIRING

Over all the wiring of this particular project became very simple with the removal of servo motors. All in all it came down to correctly wiring the router to the wall and the server to the router which is as simple as wiring the server into Ethernet port 1 on the router. We used a Backup Power supply provided by SAIT which needed to be plugged into the wall. The server is plugged into this as its power source.

6.4 SECURITY

6.4.1 – WINDOWS SERVER 2012

The security strategy when referring to the server is fairly straight forward. For starters we have accounts locked down with passwords as any good administrator should. After this we have an account based security hierarchy which is outlined in the security strategies document. Basically this document states that the root administrator on the server has access to everything read and write. Domain administrators have access to program files but no key operating systems core files. This account is designed to be the basic system troubleshooting account. The end users will have access to this account to give them basic permissions for troubleshooting. Lastly we have the usual user account. Generally speaking these user accounts will be domain user accounts and can be used to access the server. Unfortunately these accounts have no access to program files other than read, and have no access to windows 32 files. Lastly we implemented the basic windows server 2012 firewall system by providing exceptions for specific programs to write to the server. For instance we added an exception for google drive, in that it can write to the server automatically, and having its operation ports never blocked for reading or writing. Other exceptions were added such as an exception in the same way for Dropbox as this was our primary file sharing repository for the project. One of the first things we noticed is that windows server


2012 has very little free anti-virus software that runs correctly if at all on the operating system. Depending on how you look at it, this could be a very detrimental element in the architecture, or a very positive one. Considering how new the operating system is the amount of exploits discovered is fairly small. Surely enough software will be available as more exploits are discovered.

6.4.2 – RASPBERRY PI

Much like the server this little microcomputer was given accounts which require login credentials to be enabled access. Various permissions on the system were also implemented on the most basic levels using the chmod. (change permissions command) Another security element is the idea that the Raspberry Pi will have no available peripherals, thus having a only one way in to access anything on the raspberry pi and that is to SSH into it. In order to achieve this you must know the password credentials of a user account to gain access.

6.5 SERVICES

Windows Server 2012 is a powerful server operating system which enables the user to implement a great deal of services to a great deal of machines. To achieve the requirements of the project we needed to host three services to a network and successfully implement them. In reality we implemented four services including active directory and,

1. DHCP (Dynamic host configuration Protocol)

2. DNS (Domain name system)

3. NFS (Network File System)

6.5.1 DHCP

DHCP was implemented to enable next to infinite scalability on one server. Many Raspberry Pi’s can serve as nodes to receive radio frequencies. All each of these nodes needs to be accepted onto the network is to login into the default gateway (router) to access the domain. Once on the domain, the device will automatically be administered an IP address.

6.5.2 DNS

The DNS service was implemented to enable name resolution within the domain. Overall the primary focus of the service is to map out the start of authority and have DNS records relating to the server. Everything within the domain is pointing to the server as a primary source of authority on name resolution. Also this service was configured with forwarders and secondary DNS’s to work in conjunction with other DNS servers to make the internet available to machines on the domain.

6.5.3 NFSLASER-SIGHT LOCKDOWN FINAL REPORTPAGE 19

As we have a joint machine community built on our domain, we must have special services to share files between the different architectures of Linux and Windows. We used a file share between the Server and our Raspberry Pi to store photos as well as using various cloud services such as Dropbox or Google drive. Each of these places (excluding dropbox) will be updated with photo’s just in case one side of the system is down or unavailable and the data is crucial. The other reason was to have the files available on a potentially hosted website. This is somewhat of an out of scope objective, but provides a greater deal of scalability.

7.0 - PROJECT OBJECTIVES

# Problem Completed

1 Set up server to host services and meet project goal of a server setup

Yes

2 Build a Raspberry Pi to receive radio frequencies and take photos after a motion sensor trip

Yes

3 Have a largely scalable device Yes

4 Build an all in one security system Yes

Figure 16

8.0 - CHALLENGES

8.1 - WHAT DID WE FACE?

8.1.2 - CHARTER

The project got off to a rough start. Unfortunately our original project idea was not approved and we got notice of this fairly late in third semester thus making us rewrite the charter over the Christmas break. Thankfully after much thought and turmoil we came up with a new more information technology oriented project idea: a low cost security system that can be implemented without a monthly subscription fee. This particular project idea met all the requirements and allowed us to continue onto the working phase.

8.1.3 - SCOPE CREEP

Another major thing we had to overcome was the tendency to add things to the project thus creating scope creep. During the mid-point of development we found some interesting code which can find faces in a frame and lock on to them. We actually managed to get this software installed and running correctly even though it was out of scope. Thankfully only small amounts of time were used to configure this.

8.1.4 - MATERIALS LOST IN SHIPMENT


During the project we ordered some parts from overseas that were essential to our project. Some of said parts never showed up despite purchasing them. Thankfully Jason Fisher already had these parts available to loan. Such parts include the breadboard, the servo motor, and the battery pack.

Another issue we face with shipping was the fact that it took until the last third of the semester for our ninja blocks pi crust to arrive. This is a key component of our project and we were unable to work with it until it arrived in March putting us at a fairly significant inconvenience. Despite the odds, we figured out the pi crust with the help of the ninja blocks staff and pulled through by using the tools available to us from ninja blocks such as their hub and the Arduino IDE.

When you exclude the charter situation at the beginning of the semester the primary issue that we faced was dealing with long shipping times or items not showing up at all after ordering them. As one can probably imagine a lack of parts can cause any group to fall into complete panic. Despite the time crunch we held it together and got the project requirements

8.1.5 - RASPBERRY PI AND NINJA BLOCKS PI CRUST

While configuring the Raspberry Pi we we’re unable to install certain packages completely and certain files would be missing or corrupted. This issue seemed to stem from SAIT’s content blocking set up on the network. Since SAIT Polytechnic is an institute of education it is understandable that content blocking would be implemented for security purposes. This issue also conflicted with the Ninja Blocks Pi Crust as it was unable to connect to the Ninja Cloud for configuring.

8.1.6 - ARDUINO IDE

While trying to compile code on the Arduino IDE software, which is normally used to send the compiled code to the Arduino chip to be processed, the software was unable to connect to the GPIO pins which the block was connected to.

8.1.7 - SERVER

While configuring the server we installed the DNS service after DHCP. This caused the server to be unable to promote itself to the Domain Controller. This made the domain unable to be resolved.

8.1.8 - ROUTER

When we finalized the DHCP role on the server, we noticed it was not leasing addresses. After logging into the router's configuration we noticed it was acting as the DHCP server.

8.2 - HOW DID WE OVERCOME IT?

8.2.1 - CHARTER

Thankfully after much thought and turmoil we came up with a new more information technology oriented project idea: a low cost security system that can be implemented


without a monthly subscription fee. This particular project idea met all the requirements and allowed us to continue onto the working phase.

8.2.2 - MATERIALS LOST IN SHIPMENT

As one can probably imagine a lack of parts can cause any group to fall into complete panic. Despite the time crunch we held it together and got the project requirements

8.2.3 - RASPBERRY PI AND NINJA BLOCKS PI CRUST

By tethering wireless Internet access from the Raspberry Pi to a cell phone using the Samsung Galaxy S3's Wi-Fi Hotspot feature we were able to bypass SAIT's network connection entirely which led us to configure the Raspberry Pi and Ninja Blocks Pi Crust properly.

8.2.4 - ARDUINO IDE

We had to scrap this step all together. In order to properly implement servo motor control, we would have to use the Raspberry Pi CPU and install kernel modules that enabled control via the Pi's GPIO pins. This would waste CPU time on the Raspberry Pi and the kernel modules may conflict with files that the Pi Crust was using. We had an issue during configuring the Motion kernel module where the guide we were referencing told us to edit the permissions on the directory which somehow made us unable to use the command sudo essentially disabling configuration.

8.2.5 - SERVER

In order to promote the server to Domain Controller, we had to reinstall the operating system and add the DNS role before adding any other roles.

8.2.6 - ROUTER

Logging into the router's configuration, we we’re able to disable the DHCP service on the front page of the configuration.

9.0 - FURTHER DEVELOPMENT

9.1 - OPPORTUNITIES WITH THE SYSTEM

With the implementation of this system it allows people to obtain a quality security system with new age features that will also be scalable and affordable. With the project having the ability to be scaled up to whatever size is required it makes it so that users can feel secure knowing they have a system monitoring their properties and all within a desired budget. Programs such as Motion or Servoblaster can also be installed which will allow for facial recognition and motion detection within the webcam itself, though it must be installed as either a facial recognition system or as a perimeter security


system each on an individual Raspberry Pi. But nothing is stopping a user from implementing both of these systems for even more security.

9.2 - POTENTIAL RECOMMENDATIONS

As the project becomes larger and more robust, items such as weather-proof casings or humidity/temperature sensors can be added to make the system even more resilient and sophisticated.

Once more functionality is built into the Raspberry Pi’s kernel and driver functionality, the combining of the face recognition and perimeter security system will also be able to be built into one device and set up to a servo motor that would allow for physical movement of the camera systems.

10.0 - CONCLUSION

Nearing the end of our project, we started to realize that fighting with the Raspberry Pi’s drivers were going to make it too difficult to get the servo functionality to work thus, we decided to make a change request and make our project become a perimeter security system with facial recognition and servo control being hosted on another Raspberry Pi and built separately. The completed project is now a largely scalable perimeter security system that can have zones and multiple sensors built into it. The user will be notified by their preferred method and sent multiple photos of the surrounding area.


11.0 – APPENDIXES

APPENDIX A - CHARTER

https://www.dropbox.com/s/2keexicc8qcaw88/LaserSightCharter.doc

APPENDIX B – CHANGE REQUESTS

Laser-Sight LockdownScope Change RequestDate Submitted: April 7, 2014Department: PROJ 354Focus Area: Hold It Down! IndustriesProduct or Process: Servo-Motor FunctionalityProject or Organization Role: ProjectScope definitionWe will be focusing on a basic security topology for the showcase. This will include two infrared sensors, a Raspberry Pi camera attached to a servo motor, a router and a server. The server will host the database of logs from the sensors.Full documentation of the project will also be completed as well as a completed Proj354 website.Our project encompasses the connectivity of multiple components to create a robust and scalable security system. We will be creating a central hub using an HP Proliant server with a wireless router for connectivity to all other components.We will be creating a video camera using a raspberry pi, a raspberry pi camera lens, and a wireless NIC card all made specifically for a raspberry pi mini computing unit. The servo motor operates on a fairly wide setting, a setting in which we will have to manually reconfigure to better accommodate our Camera PI. Our case for the raspberry pi will also have to be modified to ensure effectiveness of our camera.Another component will be the use of infrared sensors which will be used to control/trigger the servo motor to adjust the cameras field of view. Each sensor will be positioned at a ninety degree angle away from the camera thus creating a fully covered area directly in front of the cameras field of view. Overall these three components need to communicate over a wireless network and pass data over this network to one another with ease.Also this system must have internet connectivity. This will be needed to upload video feed to dropbox or google drive, and to potentially post the feed on to our project website.


https://www.dropbox.com/s/2keexicc8qcaw88/LaserSightCharter.doc

System impactServo motor functionality will need to be removed rendering the camera to be permanently stationary.Scope change benefitProject will be able to be completed as a proof of concept.Implication of not making changeUnable to finish all the functionality in time for Wrap-Up meeting. Research and testing would need to be done to have kernel modules working side by side with the Ninja Blocks Pi Crust.


SECURITY STRATEGY

[Hold it Down! Industries]Laser Sight LockdownSecurity StrategiesTeam: Chris Buchanan, Travis Midwinter, Andrew TyukaszLaser Sight Lockdown in itself is a security system which can be applied to multiple different rooms, scenarios, and purposes. That being said security is the name of the game and we will be taking every precaution to enforce the integrity of our end goal: increase the security of any room or scenario. In order to achieve this we will be implementing various methodologies to harden the equipment virtually. The basic tactic in doing so is unanimous over all devices: Create profiles, add permissions, and remove any un-warranted commands.

Server

Upon installing the OS we will instantly create a lead admin account, this account will have prime access to everything on the server. All of the team members will know and use this account to perform admin related tasks. That being said we will create three tiers of user accounts , firstly there will be the main administrator account. This account will be what we will use to configure and create the system itself. The second tier will be for those who will maintain the system after our completion. These accounts will have access to scripts written by us in an attempt to allow said administrator to alter the functionality of our system to better accommodate their needs. We will still have the accounts locked out of core operating system files accounting for the fact that the system will most likely be operated by a regular consumer. Lastly we will have user accounts that have only read privileges on everything to allow for guests and other civilians to step in and take a look at the operating scripts. These last accounts will be most abundant, with three user accounts followed by the consumer admin account at one, and the system admin account at one as well. Once the accounts have been created, we will then go through the essential files and adjust the permissions on each based upon the user account accessing them. Lastly we will be removing any un-needed commands from the server. Seeing as this will be done on server 2012, the need for this step will be fairly minimal. 2012 is the


hardest version of server available on the market and thus requires little adjustment to maintain its security. Regardless we will be needing an anti-virus program and for the sake of saving funds we will be using Microsoft security essentials.

Raspberry Pi Camera (Raspberry Eye)

Fortunately for us this unit ships with a version of Linux known as Raspbian which is very similar to the Debian Linux release. The device will serve one purpose, and that is to become a fully functional video camera. Now that being said we will only need one admin account and another customer admin account in case the customer needs to apply any adjustments or even modifications to the system. The customer administrator account will not have access to essential files such as etc, or bin. For the most part this administrator account will have the same permissions into most files other than key Linux operating system files, and kernel files. The reason why we don’t need to add many accounts is plainly due to the fact that one would have the hook up a monitor or telnet into the PI device to even get a view into anything. The likelihood of someone needing to adjust something on our raspberry pi would be very unlikely but just in case this account will be present. Removing un-used commands will take place in the final stages of development. We will stick to this regiment to avoid any issues revolving around removing any commands we may need but don’t know it at the current time.

Router

We will be locking the router down by adding a password to connect, and have the mac address of the device connecting to our server to further verify the objects need to be on the network. Potential DNS records will be updated on the server to better accommodate the addition of cameras and devices .

Website


The main thing we will have to try and prevent is cross site scripting. Thankfully we will be using dropbox/google drive to host video feed thus eliminating the need for an SQL database and any threats associated with SQL. Add specific logon information for each online repository to keep intruders out. Also if the streamed data is being accessed on our site at any time and the access point is through a search we will need to implement anti-cross site scripting code to each search box to avoid any serious intrusion attempts.

Physical

The actual scope of our physical security will have to be determined during the development of the system. We will most likely have to create a mechanism or piece of software that recognized various objects with respect to the infrared sensors. This will be handled with some kind of script or depending on the environment, whatever coding language that the environment is based upon. To avoid any hang-ups the servo motor will default to a center position after a set amount of time. This will ensure that the camera angle will catch an intruder in any case presented.

During construction: We have a locked cabinet courtesy of Genina’s group, a non-lockable drawer monitored by a series of cameras in the lab. Our bench is no man’s land and thus only we will have access to the components on the

After construction: Have all points of potential camouflage monitored and in the field of view of our system. This will enable the user to obtain some kind of video footage of the intruder thus allowing for a better chance of catching the intruder. The infrared sensors are wide view so catching things in the field of operation should not be an issue. A lockable case for the pi will also be installed so it cannot be tampered with if someone were to get past the field of view.


APPENDIX B. - RUNTIME MANUALS

SERVER

SERVER RUNTIME MANUAL WITH WINDOWS SERVER 2012Server Install

1. On boot the server will ask for iLO configuration. This will be skipped.2. When the boot asks to configure RAID devices press F83. You will need to configure to RAID devices. Firstly, ensure there are no RAID

devices currently on the server. Configure one disk for the RAID 0. This will be used for the operating system. The other 5 disks will be configured as a RAID 5 device for storage.

4. Insert the Windows Server 2012 CD into the CD tray or however you choose to boot the operating system whether it’s through USB or PXE network boot.

5. Follow on screen instructions for installing the operating system.6. Enter a valid key for installation. Having a non-genuine version of the operating

system running is unsafe.7. Make sure you are installing the operating system on the RAID 0 device (the smaller

disk).8. Wait for the installation to finish; this will require a reboot of the machine.9. When the installation has finished you will be prompted to change the Administrator

password.10. Log in to the server.

Server Services configuration

1. Configure a static IP address and assign a computer name.a. Assign a static IP address to the server as well as add the default gateway to

internet settings. (Right click the network settings in the bottom right of your screen by the time. Open network and sharing center

Left click your connection, whether it be wired or wireless. (under access type)

Properties Scroll down to IPV4 and Left click Configure a static IP address to your will.

b. Ensure your network follows a general IP address scheme c. Enter 127.0.0.1 for primary DNS and one of your local DNS servers for the

alternate (ie. SAIT’s DNS 10.161.33.217).d. We recommend a descriptive name such as HoldItDownServ. This requires a

reboot in order to take effect.

Click Windows explorer (Bottom Left by the start button on most windows machines)


Right click Computer (left action pane) Click Properties Change Settings (bottom right quarter of the screen) Click the change button beside the “to rename this computer”

option Rename your machine.

2. By default Server Manager will open on logon (this can be disabled for quicker start up).

a. Click “Manage”b. Click “Add Roles and Features”c. Click Next after you have read the “Before You Begin” sectiond. Ensure “Role based or feature based installation”e. Select your server from the poolf. Find active directory domain services from the list

3. Add active directory domain services role plus management toolsIf your needing Name resolution in your domain please install DNS and management tools at this time, as you install Active Directory.**a. Post installationb. Click on the notification flag and click post active directory configurationc. Add a new forestd. Domain name (we specified holditdown.com)e. Functional level should remain at Windows Server 2012f. Leave “Specify domain controller capabilities” aloneg. Provide a DSRM passwordh. Leave default NetBIOS name unless you wish to change it (we changed it to

HOLDITDOWN)i. Leave all the default pathsj. The warnings relate to adding the server to a delegated domain in which it

may act as the DNS server. Due to the fact that the domain has not been created yet it is an invalid warning for this project.

k. Installl. Restart the serverm. The server should have installed DNS as well as domain controller services.**

4. The server should be promoted to domain controller at this point

Configure the DNS settings

1. Add a forwarder.2. Click the windows key.3. Select DNS from the panel layout.4. Right click your server in the topology diagram on the left pane of DNS manager.5. Select the forwarder tab.6. And use a suggested DNS forwarder such as Google (8.8.8.8) or your local DNS

(SAIT’s DNS).7. Check your delegated IP addresses in your chosen domain (in our case

holditdown.com) and make sure your server is the start of authority for the domain and that its IP address has been added to the list as “STATIC”.

8. When using Server 2012 the domain will automatically be created when DNS and Active Directory Domain Services are installed at the same time. If not, the user will need to create a forward lookup zone.

a. Click the windows key (keyboard) b. Select DNS from the tile system (windows 2012) If using another release of

server you will be directed to the start menu. From there you will need to


find the server manager. From server manager there will be a DNS management tool. Click it.

c. Once in the DNS management console refer to the action pane on the left. There your server will be listed. If not right click and add your server. Follow the wizard and ensure that you find your server via IP address or domain.

d. Right click your server on the left action pane. Look down to find “Add a forward lookup zone”

e. Follow the wizard and ensure the zone includes your domain.

Install DHCP Service

1. Start Server manager2. Click on manage in the top right3. Click “Add Roles and Features”4. Click next to pass the splash page5. Select “Role-based or feature-based installation” if it is not already selected and

click next.6. Click select a server from the server pool if not already selected, and find your

server in the list.7. Select DHCP from the list and make sure that the “include management tools”

check box is checked.8. Once pre-requisites are check click “Install”9. Once install is complete close the window.10. Open server manager11. Click the notification flag

Figure 17

12. Select DHCP post deployment configuration – complete installation13. Click Next to pass the splash page14. Select Local Administrator for the authorization15. Click complete16. Restart the server 17. Click the windows key18. Select DHCP from the tiles


19. Click the first IP address on the list (there shouldn’t be any others).20. Right click IPV421. Select “Add a new scope”22. Give a descriptive name for your scope.23. Select an IP range within your subnet (in our case 192.168.42.5-192.168.42.99)24. Configure the length of time to lease and click ok (generally 24 hours)25. Configure DHCP options screen; make sure you select “Yes I want to configure

these options now” and click next.26. Make sure the parent domain is correct and enter your servers name and address

and click add27. Once the server is validated click Next.28. WINS server add.29. Enter the WINS server name of your server (Generally all capitals of your hostname

so in our case put in HOLDITDOWNSERV.holditdown.com and click resolve).i. SAIT’s DNS address added to the forwarders tab not necessary use

8.8.8.8

Configure Router

1. In our case we are using a basic Linksys WRT54G router.2. Disable the DHCP server on the router.3. Ensure that you are using a static configuration setup.4. Configure a proper net IP address for the router with corresponding gateway and

DNS which will be your server.


Figure 18

Configure NFS sharing

1. Install “Server for NFS” role on the server.2. Open Server Manager3. Click “Manage”4. Click “Add Roles and Features”5. Click Next at the “Before you begin” section.6. Select “File and storage services”7. Click “File and iSCSI services”


8. Select “Server for NFS” (this roles is absolutely necessary for being able to share files with UNIX systems).

Figure 19

9. Click Next 10. Install and restart11. Create a folder in C:\12. Right click this folder13. Select properties14. Click the Sharing tab15. Share with Everyone (read only)16. Click Ok17. Right click Shared Folder 18. Check NFS sharing19. Manage NFS sharing20. Click Share this folder21. And apply

a. On the Raspberry Pi in /etc/fstab make an entry for the NFS share specifying the IP address of the server and the share folder (we used 192.168.42.3:/share)


RASPBERRY PI/NINJA BLOCKS PI CRUST

RASPBERRY PI/NINJA BLOCK RUNTIME MANUALREQUIRED EQUIPMENT: Raspberry Pi Model Rev. B

o SD Card (At least 8GB)o HDMI to DVI cordo USB Hub (If needed)o Keyboard/Mouseo Mini USB Power Cordo Wifi Dongle


Figure 20

Ninja Blocks Pi Crust with transceiver & receiver attached


Figure 21

Compatible Webcam

Figure 22


Computer/Laptop Case Material (ex., 3D Printed Case)

STARTING WITH THE RASPBERRY PI:1. First you will need to download and configure a 8 GB SD card to hold the operating

system and data of the Raspberry Pi onto a computer or laptopa. Format the SD card using SDFormatter which can be downloaded here:

https://www.sdcard.org/downloads/formatter_4/eula_windows/ and make sure to do a full format and set format size adjustment to on to allow for proper memory management within the card

Figure 23

b. Download and extract the operating system onto the SD card. Raspbian was used on this project which was the recommended operating system for the Pi because of the functionality, support and constant usage which allows for easier researching of topics. This is all chosen through the default install package on Raspberry Pi’s site by the name of NOOBS which stands for New Out Of Box Software. You can download the NOOBS image here: http://www.raspberrypi.org/downloads/

c. Download and extract NOOBS onto the SD card. **Be sure you have placed the files onto the SD card and not the NOOBS folder itself or the Pi will not be able to access the files**

2. You are now ready to insert the card into the Raspberry Pi and plug in all of the peripherals (monitor, USB hub, keyboard, mouse, Ethernet cable & power). At this point, hooking up the Ninja Blocks Pi Crust & webcam is a good idea to be sure that the Pi is setup with the devices at the first point of installation.


http://www.raspberrypi.org/downloads/

https://www.sdcard.org/downloads/formatter_4/eula_windows/

**You will need to start with an Ethernet connection until the Pi has been updated and properly configured for a wifi connection so the wifi dongle should not be inserted into the Pi as of yet**

Figure 24

3. Once your Raspberry Pi has started up you will be presented with an operating system selection screen. This is where you will choose Raspbian or your preferred OS and begin the installation.

4. Once Raspbian has been installed you will want to overclock the Raspberry Pi slightly from the raspi-config screen to the next step up (modest, 800 MHz) to allow for quicker installs and get the machine prepped for functionality.

5. You will then want to start the Raspberry Pi up and do the updates and upgrades for the Pi. This can be done with this command:

Sudo apt-get update && sudo apt-get upgrade

Sudo wget http://goo.gl/1B0fJ -O /usr/bin/rpi-update && sudo chmod +x /usr/bin/rpi-update

Sudo rpi-update

Figure 25

6. A text editor was needed to edit config files so download Gedit or your preferred editor.

Sudo apt-get install gedit


http://goo.gl/1B0fJ

7. This is also a good time to go into the GUI and edit the wifi settings (if you are using wifi) using the handy Wifi Config app that comes with Raspbian. Enter the GUI by typing startx into the command line. You will then be presented with a nice user space and a big Raspberry. Open the Wifi Config app and scan for your wifi signal and enter the proper credentials.

Figure 26

8. After that has been setup, then set up the network share from the server/computer/laptop to the Pi so that a file repository can be built after everything has been set up to save space on the Pi and have a central administrative station. This is done by setting up the server with an NFS share and then setting it up on the Raspberry Pi. The server setup can be found in the Server Runtime Manual. First, on our Pi, we need to make a directory and set it up with open permissions.

Sudo mkdir /mnt/share

Sudo chmod 777 /mnt/share


9. Then the nfs-common portmap needs to be installed, started, and ran on startup to allow the NFS to be setup properly.

Sudo aptitude install nfs-common portmap

Sudo service rpcbind start

Sudo update-rc.d rpcbind enable

10. After that has completed, you will want to edit the fstab file so that the mounted file system will connect everytime on startup. This can be done with this command:

Sudo gedit /etc/fstab &

And then add the following line:

192.168.x.x:/shareddirectoryname /mnt/share nfsnouser,atime,auto,rw,dev,exec,suid 0 0

To confirm that the mount works properly, insert this command into the command line:

Sudo mount –a


Figure 27

**If an error is received at this point then the IP address will need to be confirmed from the host for the NFS share, as well as make sure the /mnt/share directory has been created in the Pi with open permissions. A common problem when editing this file is missing the : (colon) between the IP address and the NFS share directory name.**

11. You will also want to set the Pi up so that it auto logs in to the account so that when all of the peripherals are detached it will still function with the rest of the project. To do this follow these commands in the terminal:

Sudo gedit /etc/inittab

Scroll down to:

1:2345:respawn:/sbin/getty 115200 tty1

And change it to:

#1:2345:respawn:/sbin/getty 115200 tty1

Then underneath that line add:


1:2345:respawn:/bin/login –f pi tty1 </dev/tty1 >/dev/tty1 2>&1

Then save, exit and restart and it should work.

12.At this point it would be a good idea to make a backup of your work so that if you have an SD card corruption error or just any issues in general, you will have an image that you can revert to. For this project, the tool Win32DiskImager was used. You can get Win32DiskImager here: http://sourceforge.net/projects/win32diskimager/files/latest/download

To use this tool, insert your SD card into your card reader. Open the program. Make sure that the drive letter selected is the proper SD card and then browse to a directory location where the backup will be saved and enter a filename such as RaspiBackup.img into the file name box. Once this is done, press read, wait till the loading bar finishes and that will then have created a first of many Pi backups.

Figure 28

BEGIN RASPBERRY PI NINJAFICATION:1. With updates complete, share folders setup and backups made, the project is now

ready to start setting up the Ninja Blocks Pi Crust! To begin this process the Ninja Blocks official site says to run the command:

wget –O – http://assets.ninjablocks.com/raspberry pi/install.sh | sudo bash

Though when this command was run, our project encountered an error with downloading the key from the keyserver. This was the solution that allowed the key to be fetched and installed properly:

Echo “deb http://releases.ninjablocks.com/ wheezy beta” > /etc/apt/souces.list.d/ninjablocks.list

Sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0E86E52B682BF664

Sudo apt-get update && sudo apt-get upgrade

Sudo apt-get install –y ninjablock

With this edit, the key should install from the keyserver without any issues and install properly.


http://releases.ninjablocks.com/

http://assets.ninjablocks.com/raspberry%20pi/install.sh

http://sourceforge.net/projects/win32diskimager/files/latest/download

Figure 29

2. After everything is downloaded and installed, the screen should be presented with an ASCII art ninja showing your NinjaBlocks version as well as the boards Serial #. This number is what will be used to pair the Ninja Blocks board to their online cloud system so make sure to write it down for later. **If you forget to write down your boards Serial # then just restart your Pi and it will appear on user login near the ASCII Ninja.**


Figure 30

You should now see the light on your Pi Crust turn from a blue to purple. This means that the Block has been successfully set up and is now looking to be paired with the Ninja Cloud.


Figure 31


Figure 32


SETTING UP THE NINJA CLOUD:1. Now that the Rapsberry Pi & Ninja Block have been configured, they need to be

paired with a Ninja Blocks Cloud account so that rules and zones for the block can be set up. You can create a Ninja Blocks account FREE by going to the URL http://a.ninja.is/born and filling out the new account form.

2. The Ninja Block now needs to be paired with the Ninja Cloud account. To do this, click the “Pair Block” button at the top of the Ninja Cloud Dashboard and it will pop up a window that will ask for the board’s serial #. Enter this and wait for the light on your Ninja Block to go from purple to a dark green. This means that the Ninja Block and the Ninja Cloud have been paired successfully. For a list of what the different LED statuses mean, a reference can be found here: http://help.ninjablocks.com/customer/portal/articles/684051-what-do-the-lights-on-my-ninja-block-mean- **If the LED on the Ninja Block remains a cyan color then there is an issue with the connection from the Block to the Cloud and you may either need to do a system restart or check that the device paired properly and has received an IP. This can be checked in the “Settings” section of the Cloud. ** ** If the LED remains a constant blue then there is either an issue with the installation of your Ninja Block or an issue with your network access/wifi connection. Going back and double checking all the original values and IP’s is usual a good starting place.**

3. Now the Block is all ready to start receiving signals from sensors and programming rules to be initiated once a sensor has been tripped. But first go to the Settings tab on the left bar and set up the Google Drive account as well as the email that will be notified once a sensor has been tripped. Go to Settings > Applications > Then enable the applications that are planned to be used with the Ninja Block like Google Drive and email.**Dropbox has a known compatibility issue where the images will not upload to the account when sensors have been tripped. Google Drive is a great alternative although it will not name the files when it is uploaded to the account.**

4. Now navigate to the Ninja Apps section of the Cloud and install the Ninja Sentinel app. This will allow for an easy administrative center to set up our zones and which sensors will be applied to those zones. Once this is installed, go back to the dashboard and set up the sensors signals with the Cloud. Click “Listen” within the RF433 widget and trigger the sensors to relay the radio frequency and have it pick up within the Cloud. You will see them pop up within the gray box and you will be able to label them as either a sensor or an actuator. Label it as a sensor as actuators are not used in this and complete the steps.


http://help.ninjablocks.com/customer/portal/articles/684051-what-do-the-lights-on-my-ninja-block-mean-

http://help.ninjablocks.com/customer/portal/articles/684051-what-do-the-lights-on-my-ninja-block-mean-

http://a.ninja.is/born

Figure 33

5. Now open up the Ninja Blocks “App” sections and open the Ninja Sentinel app. This will open up a new window where you can now set up Zones. Click the “Add New Zone” green button on the screen and start setting up the first Zone. Name the sensor whatever describes your zone best. For this project, the sensors were given a name and then a zone number was applied so that the project could basically be infinitely expandable. Once a name has been given to the zone, select PIR sensor from dropdown list and then click the blue “Listen” button. Then press your sensor and select it for the zone, click save, and that will have been the first zone set up. Do this as many times as needed and with as many sensors as required as the rules written in the next step can fire every second and work almost instantaneously.

Figure 34

**For a project using more than 8 sensors, setting up multiple Raspberry Pi Stations with a Ninja Blocks Pi Crust might be a good idea.**

6. With the zones set up and ready to fire, alerts can now be set up to notify a user when a sensor has been triggered, from where, and with all kinds of other things attached to it. For this part in Ninja Sentinel, click the “Alerts” tab and set up the alerts that are wanted. There are many selections here, all of which are very useful and offer a great way to be alerted of an event. For this project, an email alert was set up as well as a text message notification (although the phone call options looked like a great function).


Figure 35

7. Once all of this is completed you are now ready to complete the rules in the Ninja Cloud and complete the system. Do this by going to the “Rules” sections of the Cloud and making sure you are in the “Create Rules” section. The sensors that were previously set up should be seen here and ready to have rules applied to them. Select the sensor that is wanted and click next. Now if the webcam is still connected to the Pi then it should appear in the list of actions to occur after the chosen sensor has been tripped. Choose the webcam, Google, Email and for this project the changing of the Ninja Blocks eye color was also chosen to show which sensor has been tripped and if it replied to the rules properly.** The changing of the Ninja Blocks eye color can be later removed or not added at all to have full stealth of the Block.**Click next after all of the properly trip rules have been set and then name the rule. Choosing a name that summarizes what the rule does is a good idea. Also set the frequency that the rule should be set off, with 1 second being as quick as it can be applied and then save the rule. Do this step as many times as required and for the sensors that have been set up and you will then have a completely set up security system using a Raspberry Pi and Ninja Blocks Pi crust.


Figure 36

8. This is an extra step that this project took and that was to make a housing for the boards. This project used Lego and it turned out to look like this:


Figure 37


Figure 38


Figure 39


Figure 40


Figure 41


Figure 42


APPENDIX C

FIGURES

1. Figure 12. Figure 23. Figure 34. Figure 45. Figure 56. Figure 67. Figure 78. Figure 89. Figure 910. Figure 1011. Figure 1112. Figure 1213. Figure 1314. Figure 1415. Figure 1516. Figure 1617. Figure 1718. Figure 1819. Figure 1920. Figure 2021. Figure 2122. Figure 2223. Figure 2324. Figure 2425. Figure 2526. Figure 2627. Figure 2728. Figure 2829. Figure 2930. Figure 3031. Figure 3132. Figure 3233. Figure 3334. Figure 3435. Figure 3536. Figure 3637. Figure 3738. Figure 3839. Figure 3940. Figure 4041. Figure 4142. Figure 42


12.0 - REFERENCES

Small Business Innovation Research, “The SBIR Program” [Online] Available: http://www.sbir.gov/sbirsearch/detail/251621 [Accessed January 8th, 2014]

Christoph Buenger, DaSpors “Raspberry Pi as low-cost HD surveillance camera” Nov 2013 [Online] Available: http://www.codeproject.com/Articles/665518/Raspberry-Pi-as-low-cost-HD-surveillance-camera [Accessed: January 8th , 2014]

Liz “Introducing the New Out of the Box Software (NOOBS)” 2013 [Online] Available: http://www.raspberrypi.org/archives/4100 [Accessed: January 8th, 2014]

FrontierPC.com “SecurityMan SM-80 Wide-Angle PIR Motion Sensor” 2013 [Online] Available: http://www.frontierpc.com/security-surveillance/motion-sensors/motion-sensor/securityman/sm-80-wide-angle-pir-motion-sensor-1016084471.html [Accessed: January 8th, 2014]

Element 14 Community “Controlling a servo motor with the Raspberry Pi” 2013 [Online] Available: http://www.element14.com/community/community/raspberry-pi/blog/2013/02/08/controlling-a-servo-motor-with-the-raspberry-pi [Accessed: January 13th 2014]

Newark.com “Pi Cobbler Breakout Kit, Raspberry Pi” 2013 [Online] Available: http://canada.newark.com/adafruit-industries/914/pi-cobbler-breakout-kit-raspberry/dp/44W3497 [Accessed: January 12th, 2014]

Newark.com “TWIN INDUSTRIES TW-E41-1020 BREADBOARD, SOLDERLESS, 830 TIE POINTS” 2013 [Online] Available: http://canada.newark.com/twin-industries/tw-e41-1020/breadboard-solderless-830-tie/dp/56T0251 [Accessed: January 14th, 2014]

FrontierPC.com “SecurityMan SM-80 Wide-Angle PIR Motion Sensor” [Online] Available: http://www.frontierpc.com/security-surveillance/motion-sensors/motion-sensor/securityman/sm-80-wide-angle-pir-motion-sensor-1016084471.html [Accessed January 14th, 2014]

SecurityMan “SM-80” [Online] Available: http://www.securitymaninc.com/?page_id=2576 [Accessed January 14th, 2014]

SecurityMan “AIR-ALARM1 D.I.Y. WIRELESS HOME ALARM SYSTEM KIT USER MANUAL” [Online] Available: https://www.smarthomeusa.com/Products/SM-80/manuals/air-Alarm-manual-3.pdf [Accessed January 14th, 2014]

Adafruit “PIR Motion Sensor Tutorial” [Online] Available: http://www.instructables.com/id/PIR-Motion-Sensor-Tutorial/ [Accessed January 14th, 2014]

Justin Clayden “Adding 433 to your Raspberry Pi” [Online] Available: http://ninjablocks.com/blogs/how-to/7506204-adding-433-to-your-raspberry-pi [Accessed January 14th, 2014]


http://ninjablocks.com/blogs/how-to/7506204-adding-433-to-your-raspberry-pi

http://www.instructables.com/id/PIR-Motion-Sensor-Tutorial/

https://www.smarthomeusa.com/Products/SM-80/manuals/air-Alarm-manual-3.pdf

http://www.securitymaninc.com/?page_id=2576

http://www.securitymaninc.com/?page_id=2576

http://www.frontierpc.com/security-surveillance/motion-sensors/motion-sensor/securityman/sm-80-wide-angle-pir-motion-sensor-1016084471.html


http://canada.newark.com/twin-industries/tw-e41-1020/breadboard-solderless-830-tie/dp/56T0251

http://canada.newark.com/twin-industries/tw-e41-1020/breadboard-solderless-830-tie/dp/56T0251

http://canada.newark.com/adafruit-industries/914/pi-cobbler-breakout-kit-raspberry/dp/44W3497

http://canada.newark.com/adafruit-industries/914/pi-cobbler-breakout-kit-raspberry/dp/44W3497

http://www.element14.com/community/community/raspberry-pi/blog/2013/02/08/controlling-a-servo-motor-with-the-raspberry-pi

http://www.element14.com/community/community/raspberry-pi/blog/2013/02/08/controlling-a-servo-motor-with-the-raspberry-pi



http://www.raspberrypi.org/archives/4100

http://www.codeproject.com/Articles/665518/Raspberry-Pi-as-low-cost-HD-surveillance-camera

http://www.codeproject.com/Articles/665518/Raspberry-Pi-as-low-cost-HD-surveillance-camera

http://www.sbir.gov/sbirsearch/detail/251621

Christian Cawley “Build a Motion Capture Security System Using a Raspberry Pi” 2013 [Online] Available: http://www.makeuseof.com/tag/build-a-motion-capture-security-system-using-a-raspberry-pi/ [Accessed January 14th, 2014]

Ingo Ruhnke “xboxdrv” [Online] Available: http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html [Accessed January 14th, 2014]

Ninja Blocks “Ninja-fy Your Raspberry Pi” [Online] Available: http://ninjablocks.com/pages/picrust [Accessed January 14th, 2014]

Adafruit “Pi In the Sky Diagram” [Online] Available: http://www.adafruit.com/adablog/wp-content/uploads/2012/11/PiInSkyDiagram.png [Accessed January 14th, 2014]

Monoprice “3ft 28AWG High Speed HDMI to Adapter DVI Cable Ferrite Cores – Black” 2014 [Online] Available: http://www.monoprice.com/Product?c_id=102&cp_id=10231&cs_id=1023104&p_id=2661&seq=1&format=2 [Accessed February 3rd, 2014]

Christian Cawley “Setting Up Your Raspberry Pi For Headless Use With SSH” 2012 [Online] Available: http://www.makeuseof.com/tag/setting-raspberry-pi-headless-ssh/ [Accessed January 22nd, 2014]

Simon Monk “Adafruit’s Raspberry Pi Lesson 8. Using a Servo Motor” 2013 [Online] Available: http://learn.adafruit.com/downloads/pdf/adafruits-raspberry-pi-lesson-8-using-a-servo-motor.pdf [Accessed January 22nd, 2014]

RaspberryPi.org “Camera Module Setup” [Online] Available: www.raspberrypi.org/camera [Accessed January 22nd, 2014]

Amazon.com “New Learning Code Wireless Motion PIR Infrared Sensor Detector 1527 Code for GSM Burglar Alarm 100m 433mhz” 2014 [Online] Available: http://www.amazon.com/Learning-Wireless-Infrared-Detector-Burglar/dp/B00E4IG0VC/ref=sr_1_156?ie=UTF8&qid=1392241733&sr=8-156&keywords=Wireless+PIR#productDetails [Accessed January 22nd, 2014]

Alec Armstrong “Getting The Camera to Stream” 2013 [Online] Available: http://www.raspberrypi.org/forum/viewtopic.php?t=45599&p=361021 [Accessed January 22nd, 2014]

Quads “Setting up NFS for your Raspberry Pi” 2013 [Online] Available: http://perfectmancave.com/forum/showthread.php?t=38186 [Accessed February 5th, 2014]

Jeremy Morgan “How to Overclock Your Raspberry Pi” 2012 [Online] Available: http://www.jeremymorgan.com/tutorials/raspberry-pi/how-to-overclock-raspberry-pi/ [Accessed February 5th, 2014]

Raspberry Pi Projects “Install ServoBlaster Raspberry Pi and Control Servo Use Python” 2013 [Online] Available: http://www.raspiprojects.com/install-servoblaster-raspberry-pi-control-servo-python.html [Accessed February 5th, 2014]

Grintor “Pan / Tilt face tracking with the raspberry pi” 2013 [Online] Available: http://www.instructables.com/id/Pan-Tilt-face-tracking-with-the-raspberry-pi/step2/Get-your-raspberry-pi-ready/ [Accessed February 5th, 2014]


http://www.instructables.com/id/Pan-Tilt-face-tracking-with-the-raspberry-pi/step2/Get-your-raspberry-pi-ready/

http://www.instructables.com/id/Pan-Tilt-face-tracking-with-the-raspberry-pi/step2/Get-your-raspberry-pi-ready/

http://www.raspiprojects.com/install-servoblaster-raspberry-pi-control-servo-python.html

http://www.raspiprojects.com/install-servoblaster-raspberry-pi-control-servo-python.html

http://www.jeremymorgan.com/tutorials/raspberry-pi/how-to-overclock-raspberry-pi/

http://perfectmancave.com/forum/showthread.php?t=38186

http://www.raspberrypi.org/forum/viewtopic.php?t=45599&p=361021

http://www.amazon.com/Learning-Wireless-Infrared-Detector-Burglar/dp/B00E4IG0VC/ref=sr_1_156?ie=UTF8&qid=1392241733&sr=8-156&keywords=Wireless+PIR#productDetails



http://www.raspberrypi.org/camera

http://learn.adafruit.com/downloads/pdf/adafruits-raspberry-pi-lesson-8-using-a-servo-motor.pdf

http://learn.adafruit.com/downloads/pdf/adafruits-raspberry-pi-lesson-8-using-a-servo-motor.pdf

http://www.makeuseof.com/tag/setting-raspberry-pi-headless-ssh/

http://www.monoprice.com/Product?c_id=102&cp_id=10231&cs_id=1023104&p_id=2661&seq=1&format=2

http://www.monoprice.com/Product?c_id=102&cp_id=10231&cs_id=1023104&p_id=2661&seq=1&format=2

http://www.adafruit.com/adablog/wp-content/uploads/2012/11/PiInSkyDiagram.png

http://ninjablocks.com/pages/picrust

http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

http://www.makeuseof.com/tag/build-a-motion-capture-security-system-using-a-raspberry-pi/

http://www.makeuseof.com/tag/build-a-motion-capture-security-system-using-a-raspberry-pi/

Richard Hirst “ServoBlaster” [Online] Available: https://github.com/richardghirst/PiBits/blob/master/ServoBlaster/README.txt [Accessed March 5th, 2014]

Microsoft “APA, MLA, Chicago – automatically format bibliographies” 2014 [Online] Available: http://office.microsoft.com/en-us/word-help/apa-mla-chicago-automatically-format-bibliographies-HA102435469.aspx [Accessed March 5th, 2014]

MICHAEL “Raspberry Pi + PWM RGB LED Strip” 2013 [Online] Available: http://mitchtech.net/raspberry-pi-pwm-rgb-led-strip/ [Accessed March 5th, 2014]

Alex Nikolaidis “How to make a DIY home alarm system with a raspberry pi and a webcam” [Online] Available: https://medium.com/p/2d5a2d61da3d [Accessed March 5th, 2014]

Massachusetts Institute of Technology “Motion Guide – One Large Document” [Online] Available: http://www.mit.edu/activities/anime/arch/i386_rhel4/share/doc/motion-3.2.8/motion_guide.html [Accessed March 5th, 2014]

Elinux.org “Debian Auto Login” [Online] Available: http://elinux.org/RPi_Debian_Auto_Login [Accessed April 2, 2014]


http://elinux.org/RPi_Debian_Auto_Login

http://www.mit.edu/activities/anime/arch/i386_rhel4/share/doc/motion-3.2.8/motion_guide.html

http://www.mit.edu/activities/anime/arch/i386_rhel4/share/doc/motion-3.2.8/motion_guide.html

https://medium.com/p/2d5a2d61da3d

http://mitchtech.net/raspberry-pi-pwm-rgb-led-strip/

http://office.microsoft.com/en-us/word-help/apa-mla-chicago-automatically-format-bibliographies-HA102435469.aspx

http://office.microsoft.com/en-us/word-help/apa-mla-chicago-automatically-format-bibliographies-HA102435469.aspx

https://github.com/richardghirst/PiBits/blob/master/ServoBlaster/README.txt

laser-sight lockdown - proj354.comproj354.com/itcs/10to19/2014/f4/docs/hold it down... · web...

Documents