Difference between revisions of "BeagleBoard/GSoC/sdabhi23/BeagleBoneRemoteSeismometerNode"

From eLinux.org
Jump to: navigation, search
m
m
Line 42: Line 42:
 
| 6 || Deploy a network for connecting the nodes to a QCN Client hosted locally
 
| 6 || Deploy a network for connecting the nodes to a QCN Client hosted locally
 
|-
 
|-
| 7 || Develop a web dashboard which can interact with the QCN Client
+
| 7 || Deploy a network for connecting the nodes to a QCN Client hosted locally
 
|-
 
|-
 
| 8 || Testing, BUG fixing and documentation
 
| 8 || Testing, BUG fixing and documentation

Revision as of 04:57, 18 March 2018


Personal Details

Name: Shrey Dabhi
IRC: sdabhi23
Github: https://github.com/sdabhi23
LinkedIn: https://www.linkedin.com/in/sdabhi23
E-mail Address: shrey.dabhi23@gmail.com
Blogs: https://droidlearner.wordpress.com, https://sdabhi23.wordpress.com
School: Institute of Technology, Nirma University
Country: India
Primary Languages: English, Hindi
Typical work hours: 11 - 14, 16 - 20, 21 - 23 IST

Past Open Source Contributions

I have recently been involved in contributing to Hasura. Here's the link to one of my contributions: https://hasura.io/hub/projects/sdabhi23/currency-bot. But i haven't made any large contributions to any large open source communities, reason being I wanted to know the technologies being used before I go ahead and start working with large oraganisations and their codebases.

I am interested in contributing to BeagleBoard as majority of my work experience has been in the software domain, and I would like to better understand the hardware side of devices I work with. Also BeagleBoard has an awesome global community of developers and users.

Project Description

The aim of the project is to create a prototype network of seismometer nodes. The current proposal aims to have a prototype of sensor node of the network which can communicate with a QCN Client wirelessly. A web-based dashboard also needs to be implemented for the control and monitoring of the network.

Timeline

This project will be implemented over 12 weeks. The tentative timeline I have prepared is as follows:

Week Plan
1 Research and reading for finding the best accelerometer sensor for the given use case and appropriate library interface
2 Study of internal working of the QCN Client software
3 Develop a seismometer node and calibrate it to the best precision level possible
4 Develop a seismometer node and calibrate it to the best precision level possible
5 Testing, BUG fixing and documentation
6 Deploy a network for connecting the nodes to a QCN Client hosted locally
7 Deploy a network for connecting the nodes to a QCN Client hosted locally
8 Testing, BUG fixing and documentation
9 Develop a web dashboard which can interact with the QCN Client
10 Develop a web dashboard which can interact with the QCN Client
11 Testing, BUG fixing and documentation
12 Testing, BUG fixing and documentation

The major reason for dedicating 4 weeks to bug fixing and documentation is because the calibration process can pose some currently unforeseen challenges.

Experience and Approach

  • I have done projects with Arduino and Bluetooth technology. Also I have some experience with Raspberry PI.
  • I was easily able to deploy a similar project as described here using Arduino Nano and ADXL335 accelerometer. But the proposed project is different in the sense that a complete network of interconnected nodes will be deployed which will communicate with a single client server.

Contingency

I can use the vast documentation and help available through forums, wikis, IRC and other means to find solutions for my problems. And also as a last resort I can also consult my colleagues and other faculties in my university for further support.

Benefits

To make a less expensive, hackable and easy to deploy network for hobbyists and researchers alike to monitor seismic activities in their region.