ECE497 Project: Local Air Traffic Radio

From eLinux.org
Revision as of 04:54, 31 October 2017 by Bretscak (talk | contribs) (created new project page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Team members: Adam Bretsch

Grading Template

I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!

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 Late
Comments: I'm looking forward to seeing this.

Score:  10/100

(Inline Comment)

Executive Summary

RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals operate in two different frequency bands, 1090MHz and 978MHz. The goal of this project is to combine and display both frequency ranges using 2 SDRs, one set to each frequency range.

Currently the utilities dump1090 and dump978 can separately output plane data to a html page. This page shows the direction and location of each plane in sensor range, but only those of the selected frequency band.

The plan is to create a new utility that combines the two, showing both types of plane on one html map. The frequency range should be easily identifiable, coded by color or otherwise apparent.

This tool will have many different applications. The overall goal is to be able to set up the BeagleBone with the 2 SDRs and have it give alerts whenever a plane is close enough see. These planes will be drawn from both bands thanks to the utility designed in this project.

Packaging

If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.

Installation Instructions

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

  • Include your github path as a link like this to the read-only git site: 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 Makefile for you code.
  • Include any additional packages installed via apt.
  • 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 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.