View source for Weather station (Server side) - Team 03

[[Category:ECE597 |P3]]

Team members: [[user:Tshrjn | Tushar Jain]],| [[user:sanjeev_k | Sanjeev Khare]], | [[user:merlin sundar | Merlin sundar]]
<!--
== Grading Template ==
I'm using the following template to grade.  Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions 
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Not Late
Comments: I'm looking forward to seeing this.

Score:  00/100
</pre>

<span style="color:red">(Inline Comment)</span>
-->

==Introduction==
This project is a part of larger project which aims at collecting, storing and analyzing weather related data of a given location, currently it is Mandi, H.P., India. This team has been tasked at maintaining a server to collect and to transfer data, from sensor team to display team. 
== Executive Summary ==

The goal of this project was to build and deploy a remote data network to gather environmental
data from around campus and display it on a standard web interface.

The server runs an opensource data gathering software, Phant
and relays data to display team to be presented in graphical form on a web server (Plotly, Flot, Google Charts, Initial 
State, etc.).

The Phant currently works on port 8080. Data must sent to the server by visinting a url which has public key of the stream and field values in it.The data can be access at any time by visiting a link in many formats like csv, json and jsonp.

As mentioned above phat runs on port 8080, which is also the default port of apache server running on the beaglebone. Thus we had to shut down apache server to run phant. Phant has also been susceptible to crashing down when the network is probed with nmap.

 

== Equipment needed ==
Beaglebone to run a server on, Lan network and wifi adapter or wired connection or a system which has a port forwarded to the bone.

==User Instruction==
This server is almost completely automated. After installation you need power up the bone and make sure that it is connected to the network. 

==Installation Notes==

Installing phant behind a proxy can be tricky. 

Be sure to set npm proxy. Using

<code>npm config set proxy http://10.8.0.1:8080</code>
<code>npm config set https-proxy http://10.8.0.1:8080</code>

also you might have to give proxy as a cmd argument as

<code>npm --http-proxy=http://10.8.0.1:8080 install -g whatevef </code>

You can also pass proxy as environment variables, as

<code>npm npm_config_proxy http://proxy:port</code>

Then install phant via npm package.

<div class="highlight"><pre>root@beaglebone:~# npm install -g phant
 npm http GET https://registry.npmjs.org/phant
 npm http <span class="m">304</span> https://registry.npmjs.org/phant
</pre></div>

This should install phant on the bone.

You must also export the system proxy on your bone with

<code> export http_proxy=http://proxy:port</code>
<code> export https_proxy=https://proxy:port</code>

Make sure to export both http and https.

==Post installation steps==

You must stop apache running on 8080 and start Phant. for this 
<code>sudo service stop apache2 </code>

1.type in <code>phant</code> (command prompt)
      phant starts up…
      2.   phant http server running on port 8080
           phant telnet server running on port 8081
      3.  telnet beaglebone.local 8081

You must create a stream on phat where data will be logged into. Note down the keys as you will need them later and you cannot re-generate them. 

Creating Stream :
<div class="highlight"><pre>
phant> create 
Enter a title> Data_Test
Enter a description> just_a_test
Enter fields (comma separated)> temp,wind,rain,humidity 
Enter tags (comma separated)> weather data

Stream created!
 PUBLIC KEY: ******
 PRIVATE KEY:  *****
 DELETE KEY:  *****
</pre></div>

This creates a stream to log data. 

A second and easier method is to the web gui provided in phant, which you can access by 

<code>http://beaglebone.local:8080/</code>

==Usage==
Use the following step to log data to the server, you must enter this url on your web browser:
<code>http://beaglebone.local:8080/input/PUBLIC_KEY?private_key=PRIVATE_KEY&test=testvalue</code>

where beaglebone.local:port = 192.168.7.2:8080, if you are logging data to a bone connected directly to your system, otherwise if bone is connected to a network enter the ip of the bone on the network.  

And to retrieve Data we used the following url:
http://beaglebone.local:8080/output/PUBLIC_KEY.<enter your desire format>


If your bone is not connected directly to the network, then to directly log data to beaglebone via an unconnected host we used postForward.sh which forwards the port to a connected host in turn connecting the desired host to the bone. This script is provided in the link given below in setup directory. This provided by Prof. Mark A. Yoder.
<code>https://github.com/MarkAYoder/BeagleBoard-exercises</code>

The whole process can be automated by running a file which uses crontab, given here

<code> https://github.com/sanjekhare/team1_server</code>

== Highlights ==
Also this is the server side of project thus it does not play a very visible role in it, it does has its special features. The server which we have setup is completely automated. All end user has to do is to power it up and be sure to provide it a static ip on the network. 

This server also create a back up, in case of network failures. 
== Theory of Operation ==

== Work Breakdown ==
Installing, setting up phant and port forwarding over the network was done by Sanjeev Khare, b13266. 
Automating the whole process of starting the phant server when the bone was powered on and creating a back up was done by Tushar Jain, b13236.

== Current State ==
Completed

== Future Work ==

We will then try to patch the nmap bug. Software to archive data  so that it could be sent to display team needs to be investigated. 
Team Server
This team of two students will look at the server that archives all the data. Currently the system uses Phant as the server, but there are other systems available.  This team will 
discover what other options are available, 
install, test and evaluate them and
recommend and implement one for the project.
we may look into socket.io

Instruction to setup socket are provide here <code>https://docs.google.com/document/d/1ifBIIhB8_Ozc-dCVj4NCb9MSygaXBei5mNQ7AB_S9Zg/edit?usp=sharing</code>.

==Links==

Our google doc folder

<code>https://drive.google.com/open?id=1pHZot5EtbzWs6ITb87KqPdPUZJ0W9H0twWsBsYtZ8Eo/</code>.

Our Github repo

<code>https://docs.google.com/document/d/1ifBIIhB8_Ozc-dCVj4NCb9MSygaXBei5mNQ7AB_S9Zg/edit?usp=sharing</code>

Prof. Mark A. Yoders github repo

<code>https://github.com/MarkAYoder/BeagleBoard-exercises</code>.

Phant official website

<code>http://phant.io/</code>.

== Conclusions ==

<!--
Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.
-->
<!--
== Packaging ==

If you have hardware, consider [http://cpprojects.blogspot.com/2013/07/small-build-big-execuition.html Small Build, Big Execuition] for ideas on the final packaging.

If you have wiring, include Frizing diagrams.

== Installation Instructions ==

Give step by step instructions on how to install your project.  

* Include your [https://github.com/ github] path as a link like this to the read-only git site:  [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn]. 
* Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
* Include a file called '''install.sh''' which installs all the files/packages needed. These are the things that only need to be done one.
* Include a file called '''setup.sh''' which initializes everything.  These are the things that need to be done every time you reboot the Bone.
* Include a Makefile for your code if you use a compiled language.
* Include any additional packages installed via '''apt-get'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program?  Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software.  Are you using GStreamer?  Show a diagram of the pipeline.  Are you running multiple tasks?  Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}} -->