Difference between revisions of "F18: Wireless sensor network"

Revision as of 23:37, 27 November 2018

Grading Criteria

How well is Software & Hardware Design described?
How well can this report be used to reproduce this project?
Code Quality
Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
  Schematic Quality
- Quality of technical challenges and solutions adopted.

Wireless Sensor Network

Abstract

A wireless sensor network (WSN) consists of collection of sensor nodes. Each individual node consists of MCU with on-board sensors and Nordic wireless mesh for communication, which are distributed to monitor physical or environmental conditions, such as temperature, ambient light, humidity etc. The SJ-One board contains an onboard light intensity sensor, and a custom PCB for the project has a combined Temperature, Pressure, and Humidity sensor and an air quality sensor. These sensor data are transmitted to a network coordinator which is the controls the wireless mesh network. The advantage of a mesh configuration is that the data flow is uninterrupted in the network even if one of the nodes fails. The coordinator board colates the data from all nodes, and displays it on a 16x32 LED matrix.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

Halak Vyas
- RTC Config (primary), Wireless driver (secondary), Sensor drivers
Jay Parsana
- Display driver (primary), Sensor drivers
Prashant Gandhi
- PCB Assembly, PCB Design (review), Sensor drivers
Tristan French
- Team lead, PCB Design (primary), PCB Assembly (secondary), Display driver (secondary)
Vatsal Makani
- Wireless driver (Primary), PCB design (secondary), Wiki lead

Schedule

Week#	Date	Task	Actual
1	10/9	Tristan Order LED matrix Everyone Assign team roles	Tristan Matrix ordered (10/1), Received (10/14) Everyone Team roles assigned (10/16)
2	10/16	Everyone Create wiki schedule	Everyone Initial schedule created(10/16). Unforeseen issues Issues with wiki login credentials (resolved) Discovered antennas that we have do not match the connector, must order new ones (resolved)
3	10/23	Vatsal Order antenna adapters	Vatsal adapters ordered
4	10/30	Halak RTC programming started Tristan PCB design requirements complete	Halak RTC programming started Tristan PCB Design requirements delayed, still finalizing sensors.
5	11/6	Halak task Jay Acquire power supply for LED matrix, review Adafruit library Prashant Review and update schedule for your subsystem. Tristan PCB design complete and ordered (including components) Vatsal Review nordic wireless API, and plan code	Halak Completed? Jay Acquired (Tristan already had a power supply) Prashant Schedule updated Tristan Poor documentation on MQ-135, waiting for parts before releasing PCB. Design 95% complete Vatsal Investigated, have questions for Preet next week
6	11/13	Halak RTC programming done Jay Initial LED matrix testing Prashant Review PCB design Tristan PCB and components Ordered Vatsal Basic wireless driver (send/receive a byte)	Halak RTC code complete, need battery to test. Jay LED matrix initial test completed (able to light desired LED). Prashant Reviewed and approved Tristan PCB ordered (11/10) arriving 11/15. Vatsal Wireless not functioning yet, Prashant and Halak to provide support.
7	11/20	Halak Write initial driver to read BME280 sensor values Jay Display symbols on matrix Prashant Write MQ-135 sensor driver and test Tristan PCB Soldered Vatsal Wireless driver send/receive sensor data	Halak Able to read raw data values Jay Displaying letters and numbers Prashant Code written to read MQ-135, need to test Tristan One PCB soldered and initial test completed Vatsal Initial transmitter code complete, receiver mostly complete, troubleshooting
8	11/27	Halak Finish BME280 Driver Jay Parse and display ASCII sensor data Prashant Finish MQ-135 driver Solder remaining PCBs Tristan Solder remaining PCBs Vatsal Wireless driver code to Send and Receive Sensor Data	Halak Completed? Jay Completed? Prashant Completed? Tristan Completed? Vatsal Completed?
9	12/4	Halak Make BME280 data accessible by wireless module Jay Read and display Sensor display from wireless, and switch between display devices Prashant Make MQ-135 data accessible by wireless module Tristan Support integration Vatsal Make received sensor data available to display driver Everyone Integration of all drivers/modules, All sensor readings working	Halak Completed? Jay Completed? Prashant Completed? Tristan Completed? Vatsal Completed? Everyone Completed?
10	12/11	Everyone Debugging any major issues, Project complete	Everyone Completed?
11	12/19	Everyone Final code cleanup and testing. Project Demo and Review day	Everyone Completed?

Parts List & Cost

Item#	Part	Manufacturer	Quantity	Unit Cost($)	Total Cost($)
1	SJ One Board	Preet	5	80.00	400.00
2	Adafruit RGB LED Matrix	LED Matrix	1	24.95	24.95
3	Led Matrix Power Adapter	N/A (Stock)	1	N/A	0.00
4	Air Quality Sensor	Willwin	4	4.50	18.00
5	Custom Sensor PCB	JLCPCB	4	0.20	0.80
6	....	....	x	x.00	x.00

Total Cost:

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Sensor PCB

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

1. In Wireless Tx section, mesh_init() needs a parameter of type mesh_driver which needs some initialization. In Wireless Rx section, ensuring the receipt of packets needs some review.

2. Calibration of Air Quality Sensor and Temperature/Humidity/Pressure sensor is a challenging part.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

Sourceforge Source Code Link

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.

@@ Line 186: / Line 186: @@
 * Completed?
 Vatsal
-* Completed?
-Everyone
 * Completed?<!--