https://elinux.org/api.php?action=feedcontributions&user=Bretscak&feedformat=atomeLinux.org - User contributions [en]2024-03-28T23:48:22ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=466811ECE497 Project: Local Air Traffic Radio2018-03-28T01:30:14Z<p>Bretscak: /* Grading */</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals include much information about the flight, including latitude, longitude, height and other flight charactertics.<br />
<br />
Currently the utility dump1090 can output plane data to a html page. This page shows the direction and location of each plane in sensor range, but is only accessible in the local network.<br />
<br />
The goal of this project is to create a device that will track the local air traffic and alert the user whenever a plane comes close enough to look out the window and see<br />
<br />
This tool will have many different applications. The overall goal is to be able to set up the BeagleBone with an SDR and have it give alerts whenever a plane is close enough to see. These planes will be found using the dump1090 utility and the system will alert the user via both a buzzer and by tweeting the plane's information at https://twitter.com/FlightsOverRose .<br />
== Packaging ==<br />
Components used are listed below:<br />
<br />
BeagleBone Blue:<br />
https://beagleboard.org/blue<br />
<br />
Software Defined Radio:<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
Electronic Buzzer:<br />
https://www.adafruit.com/product/1536<br />
<br />
== Installation Instructions ==<br />
<br />
This program relies on several utilities. Most of them are python specific and can be installed with the python utility of pip. This can be accomplished with the commands:<br />
pip install tweepy<br />
pip install geopy<br />
For the buzzer, the library adafruit BBIO is used for GPIO. it can be found and installed from https://github.com/adafruit/adafruit-beaglebone-io-python . The buzzer is connected to GP1_5, also known as LED_RED.<br />
<br />
The main repo is:<br />
https://github.com/AdamBretsch/SDRFlights<br />
This includes the dump1090 utility, prebuilt and ready to use. No compiling is needed before running. This utility is originally from https://github.com/mutability/dump1090. <br />
<br />
== User Instructions ==<br />
<br />
After cloning the repo, plug in the SDR. I've found that using a externally powered usb hub can improve signal strength. Connect to the BeagleBone and make sure it has Internet access. From here, navidate to the SDRFlights directory and run the scripts ./localdumo.sh, HTTPserver.sh and tweetPlanes.py to run the utility. The raw HTML data can be found at 192.168.7.2:8090/gmap.html. The console should readout any tweets, as well as updating the actual twitter at https://twitter.com/FlightsOverRose . Whenever a plane passes overhead, the buzzer will beep and the twitter account will update with the new information.<br />
<br />
== Highlights ==<br />
<br />
Example of use:<br />
https://www.youtube.com/watch?v=JTODDWsaSgg<br />
<br />
Past tweets:<br />
https://twitter.com/FlightsOverRose<br />
<br />
== Theory of Operation ==<br />
<br />
The utility dump1090 calibrates and begins the SDR's collection of data. The script begindump.sh starts this process and starts dump1090 with the option to deposit all data gathered into a .json file ./dump1090/public_html/data/aircraft.json. Using the script ./HTMLserver.sh, a basic python html server is started on port 8090 that views that data in an html form.<br />
<br />
For my project, the same aircraft.json file that serves the html page is queried and used to compile data on the local flights. The program ./listPlanes.py gathers this data and filters out the planes that don't have a strong enough signal to give specific aircraft information such as flight number or speed. If this information is present, each plane and its values are recorded, and the distance to each plane from the local position (currently assume to be Rose-Hulman in Terre Haute, IN) is calculated using geopy's vincety distance between two points in the form (latitude, longitude). This program was the first step in processing the information used in the project, and can currently be used to check the distance to each fully visible plane.<br />
<br />
In ./tweetPlanes.py, ./listPlanes.py has been expanded to include the functionality to tweet and activate a buzzer to inform the user whenever a plane is close enough to be locally seen. The distance is set to 20 miles by default, and whenever a plane is detected within this distance, a tweet including its flight number, distance, speed, altitude, and a link to a third party flight-tracker is included in the tweet. The twitter feed operates through use of the utility tweepy, which integrates with a custom-made application on apps.twitter.com, communicating via public and private keys to the twitter account.<br />
<br />
== Work Breakdown ==<br />
<br />
Installed dump1090 - 10/22/17<br />
<br />
Tested dump1090 -10/22/17<br />
<br />
Installed dump978 - 10/29/17<br />
<br />
Tested dump978 - 10/29/17<br />
<br />
Analyze dump1090 source - 11/2/17<br />
<br />
Create listPlanes.py program - 11/5/17<br />
<br />
Finish implementation of listPlanes.py - 11/6/17<br />
<br />
Create tweetPlanes.py - 11/7/17<br />
<br />
Finish implementation of tweetPlanes.py 11/10/17<br />
<br />
Finish documentation on wiki - 11/13/17<br />
<br />
== Future Work == <br />
<br />
A great deal of time was spent trying to integrate planes from the 978 MHz band using another utility dump978, but the information was presented in a different manner that I found difficult to integrate into the project. This is possible however, and would expand the usefulness of the tool.<br />
<br />
More information from the flight, such as flight origin and destination could be included.<br />
<br />
Weather information could be pulled from an open API, and visibility information could be used to make sure all planes that trigger an alert are actually in the seeable range.<br />
<br />
== Conclusions ==<br />
This project has been quite a learning experience for me. I've never before worked with both .json files or twitter, so learning to use both has been a learning experience. My original project goal was to combine the dump1090 and dump978 utilities, but I could never get the dump978 program to fully function, so I switched the scope of the project to the current scope, which has worked out well. I think the project turned out great, with a solid product thats rather fun to play with.</div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=456336ECE497 Project: Local Air Traffic Radio2017-11-14T15:05:16Z<p>Bretscak: </p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals include much information about the flight, including latitude, longitude, height and other flight charactertics.<br />
<br />
Currently the utility dump1090 can output plane data to a html page. This page shows the direction and location of each plane in sensor range, but is only accessible in the local network.<br />
<br />
The goal of this project is to create a device that will track the local air traffic and alert the user whenever a plane comes close enough to look out the window and see<br />
<br />
This tool will have many different applications. The overall goal is to be able to set up the BeagleBone with an SDR and have it give alerts whenever a plane is close enough to see. These planes will be found using the dump1090 utility and the system will alert the user via both a buzzer and by tweeting the plane's information at https://twitter.com/FlightsOverRose .<br />
== Packaging ==<br />
Components used are listed below:<br />
<br />
BeagleBone Blue:<br />
https://beagleboard.org/blue<br />
<br />
Software Defined Radio:<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
Electronic Buzzer:<br />
https://www.adafruit.com/product/1536<br />
<br />
== Installation Instructions ==<br />
<br />
This program relies on several utilities. Most of them are python specific and can be installed with the python utility of pip. This can be accomplished with the commands:<br />
pip install tweepy<br />
pip install geopy<br />
For the buzzer, the library adafruit BBIO is used for GPIO. it can be found and installed from https://github.com/adafruit/adafruit-beaglebone-io-python . The buzzer is connected to GP1_5, also known as LED_RED.<br />
<br />
The main repo is:<br />
https://github.com/AdamBretsch/SDRFlights<br />
This includes the dump1090 utility, prebuilt and ready to use. No compiling is needed before running. This utility is originally from https://github.com/mutability/dump1090. <br />
<br />
== User Instructions ==<br />
<br />
After cloning the repo, plug in the SDR. I've found that using a externally powered usb hub can improve signal strength. Connect to the BeagleBone and make sure it has Internet access. From here, navidate to the SDRFlights directory and run the scripts ./localdumo.sh, HTTPserver.sh and tweetPlanes.py to run the utility. The raw HTML data can be found at 192.168.7.2:8090/gmap.html. The console should readout any tweets, as well as updating the actual twitter at https://twitter.com/FlightsOverRose . Whenever a plane passes overhead, the buzzer will beep and the twitter account will update with the new information.<br />
<br />
== Highlights ==<br />
<br />
Example of use:<br />
https://www.youtube.com/watch?v=JTODDWsaSgg<br />
<br />
Past tweets:<br />
https://twitter.com/FlightsOverRose<br />
<br />
== Theory of Operation ==<br />
<br />
The utility dump1090 calibrates and begins the SDR's collection of data. The script begindump.sh starts this process and starts dump1090 with the option to deposit all data gathered into a .json file ./dump1090/public_html/data/aircraft.json. Using the script ./HTMLserver.sh, a basic python html server is started on port 8090 that views that data in an html form.<br />
<br />
For my project, the same aircraft.json file that serves the html page is queried and used to compile data on the local flights. The program ./listPlanes.py gathers this data and filters out the planes that don't have a strong enough signal to give specific aircraft information such as flight number or speed. If this information is present, each plane and its values are recorded, and the distance to each plane from the local position (currently assume to be Rose-Hulman in Terre Haute, IN) is calculated using geopy's vincety distance between two points in the form (latitude, longitude). This program was the first step in processing the information used in the project, and can currently be used to check the distance to each fully visible plane.<br />
<br />
In ./tweetPlanes.py, ./listPlanes.py has been expanded to include the functionality to tweet and activate a buzzer to inform the user whenever a plane is close enough to be locally seen. The distance is set to 20 miles by default, and whenever a plane is detected within this distance, a tweet including its flight number, distance, speed, altitude, and a link to a third party flight-tracker is included in the tweet. The twitter feed operates through use of the utility tweepy, which integrates with a custom-made application on apps.twitter.com, communicating via public and private keys to the twitter account.<br />
<br />
== Work Breakdown ==<br />
<br />
Installed dump1090 - 10/22/17<br />
<br />
Tested dump1090 -10/22/17<br />
<br />
Installed dump978 - 10/29/17<br />
<br />
Tested dump978 - 10/29/17<br />
<br />
Analyze dump1090 source - 11/2/17<br />
<br />
Create listPlanes.py program - 11/5/17<br />
<br />
Finish implementation of listPlanes.py - 11/6/17<br />
<br />
Create tweetPlanes.py - 11/7/17<br />
<br />
Finish implementation of tweetPlanes.py 11/10/17<br />
<br />
Finish documentation on wiki - 11/13/17<br />
<br />
== Future Work == <br />
<br />
A great deal of time was spent trying to integrate planes from the 978 MHz band using another utility dump978, but the information was presented in a different manner that I found difficult to integrate into the project. This is possible however, and would expand the usefulness of the tool.<br />
<br />
More information from the flight, such as flight origin and destination could be included.<br />
<br />
Weather information could be pulled from an open API, and visibility information could be used to make sure all planes that trigger an alert are actually in the seeable range.<br />
<br />
== Conclusions ==<br />
This project has been quite a learning experience for me. I've never before worked with both .json files or twitter, so learning to use both has been a learning experience. My original project goal was to combine the dump1090 and dump978 utilities, but I could never get the dump978 program to fully function, so I switched the scope of the project to the current scope, which has worked out well. I think the project turned out great, with a solid product thats rather fun to play with.<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=456311ECE497 Project: Local Air Traffic Radio2017-11-14T13:59:13Z<p>Bretscak: added conclusions</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals include much information about the flight, including latitude, longitude, height and other flight charactertics.<br />
<br />
Currently the utility dump1090 can output plane data to a html page. This page shows the direction and location of each plane in sensor range, but is only accessible in the local network.<br />
<br />
The goal of this project is to create a device that will track the local air traffic and alert the user whenever a plane comes close enough to look out the window and see<br />
<br />
This tool will have many different applications. The overall goal is to be able to set up the BeagleBone with an SDR and have it give alerts whenever a plane is close enough to see. These planes will be found using the dump1090 utility and the system will alert the user via both a buzzer and by tweeting the plane's information at https://twitter.com/FlightsOverRose .<br />
== Packaging ==<br />
Components used are listed below:<br />
<br />
BeagleBone Blue:<br />
https://beagleboard.org/blue<br />
<br />
Software Defined Radio:<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
Electronic Buzzer:<br />
https://www.adafruit.com/product/1536<br />
<br />
== Installation Instructions ==<br />
<br />
This program relies on several utilities. Most of them are python specific and can be installed with the python utility of pip. This can be accomplished with the commands:<br />
pip install tweepy<br />
pip install geopy<br />
For the buzzer, the library adafruit BBIO is used for GPIO. it can be found and installed from https://github.com/adafruit/adafruit-beaglebone-io-python . The buzzer is connected to GP1_5, also known as LED_RED.<br />
<br />
The main repo is:<br />
https://github.com/AdamBretsch/SDRFlights<br />
This includes the dump1090 utility, prebuilt and ready to use. No compiling is needed before running. This utility is originally from https://github.com/mutability/dump1090. <br />
<br />
See README.md in the SDRFlights github directory for more detailed install information.<br />
<br />
== User Instructions ==<br />
<br />
After cloning the repo, plug in the SDR. I've found that using a externally powered usb hub can improve signal strength. Connect to the BeagleBone and make sure it has Internet access. From here, navidate to the SDRFlights directory and run the scripts ./localdumo.sh, HTTPserver.sh and tweetPlanes.py to run the utility. The raw HTML data can be found at 192.168.7.2:8090/gmap.html. The console should readout any tweets, as well as updating the actual twitter at https://twitter.com/FlightsOverRose . Whenever a plane passes overhead, the buzzer will beep and the twitter account will update with the new information.<br />
<br />
== Highlights ==<br />
<br />
Example of use:<br />
https://www.youtube.com/watch?v=JTODDWsaSgg<br />
<br />
== Theory of Operation ==<br />
<br />
The utility dump1090 calibrates and begins the SDR's collection of data. The script begindump.sh starts this process and starts dump1090 with the option to deposit all data gathered into a .json file ./dump1090/public_html/data/aircraft.json. Using the script ./HTMLserver.sh, a basic python html server is started on port 8090 that views that data in an html form.<br />
<br />
For my project, the same aircraft.json file that serves the html page is queried and used to compile data on the local flights. The program ./listPlanes.py gathers this data and filters out the planes that don't have a strong enough signal to give specific aircraft information such as flight number or speed. If this information is present, each plane and its values are recorded, and the distance to each plane from the local position (currently assume to be Rose-Hulman in Terre Haute, IN) is calculated using geopy's vincety distance between two points in the form (latitude, longitude). This program was the first step in processing the information used in the project, and can currently be used to check the distance to each fully visible plane.<br />
<br />
In ./tweetPlanes.py, ./listPlanes.py has been expanded to include the functionality to tweet and activate a buzzer to inform the user whenever a plane is close enough to be locally seen. The distance is set to 20 miles by default, and whenever a plane is detected within this distance, a tweet including its flight number, distance, speed, altitude, and a link to a third party flight-tracker is included in the tweet. The twitter feed operates through use of the utility tweepy, which integrates with a custom-made application on apps.twitter.com, communicating via public and private keys to the twitter account.<br />
<br />
== Work Breakdown ==<br />
<br />
Installed dump1090 - 10/22/17<br />
<br />
Tested dump1090 -10/22/17<br />
<br />
Installed dump978 - 10/29/17<br />
<br />
Tested dump978 - 10/29/17<br />
<br />
Analyze dump1090 source - 11/2/17<br />
<br />
Create listPlanes.py program - 11/5/17<br />
<br />
Finish implementation of listPlanes.py - 11/6/17<br />
<br />
Create tweetPlanes.py - 11/7/17<br />
<br />
Finish implementation of tweetPlanes.py 11/10/17<br />
<br />
Finish documentation on wiki - 11/13/17<br />
<br />
== Future Work == <br />
<br />
A great deal of time was spent trying to integrate planes from the 978 MHz band using another utility dump978, but the information was presented in a different manner that I found difficult to integrate into the project. This is possible however, and would expand the usefulness of the tool.<br />
<br />
More information from the flight, such as flight origin and destination could be included.<br />
<br />
Weather information could be pulled from an open API, and visibility information could be used to make sure all planes that trigger an alert are actually in the seeable range.<br />
<br />
== Conclusions ==<br />
This project has been quite a learning experience for me. I've never before worked with both .json files or twitter, so learning to use both has been a learning experience. My original project goal was to combine the dump1090 and dump978 utilities, but I could never get the dump978 program to fully function, so I switched the scope of the project to the current scope, which has worked out well. I think the project turned out great, with a solid product thats rather fun to play with.<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=456291ECE497 Project: Local Air Traffic Radio2017-11-14T13:09:48Z<p>Bretscak: updated instructions</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals include much information about the flight, including latitude, longitude, height and other flight charactertics.<br />
<br />
Currently the utility dump1090 can output plane data to a html page. This page shows the direction and location of each plane in sensor range, but is only accessible in the local network.<br />
<br />
The goal of this project is to create a device that will track the local air traffic and alert the user whenever a plane comes close enough to look out the window and see<br />
<br />
This tool will have many different applications. The overall goal is to be able to set up the BeagleBone with an SDR and have it give alerts whenever a plane is close enough to see. These planes will be found using the dump1090 utility and the system will alert the user via both a buzzer and by tweeting the plane's information at https://twitter.com/FlightsOverRose .<br />
== Packaging ==<br />
Components used are listed below:<br />
<br />
BeagleBone Blue:<br />
https://beagleboard.org/blue<br />
<br />
Software Defined Radio:<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
Electronic Buzzer:<br />
https://www.adafruit.com/product/1536<br />
<br />
== Installation Instructions ==<br />
<br />
This program relies on several utilities. Most of them are python specific and can be installed with the python utility of pip. This can be accomplished with the commands:<br />
pip install tweepy<br />
pip install geopy<br />
For the buzzer, the library adafruit BBIO is used for GPIO. it can be found and installed from https://github.com/adafruit/adafruit-beaglebone-io-python . The buzzer is connected to GP1_5, also known as LED_RED.<br />
<br />
The main repo is:<br />
https://github.com/AdamBretsch/SDRFlights<br />
This includes the dump1090 utility, prebuilt and ready to use. No compiling is needed before running. This utility is originally from https://github.com/mutability/dump1090. <br />
<br />
See README.md in the SDRFlights github directory for more detailed install information.<br />
<br />
== User Instructions ==<br />
<br />
After cloning the repo, plug in the SDR. I've found that using a externally powered usb hub can improve signal strength. Connect to the BeagleBone and make sure it has Internet access. From here, navidate to the SDRFlights directory and run the scripts ./localdumo.sh, HTTPserver.sh and tweetPlanes.py to run the utility. The raw HTML data can be found at 192.168.7.2:8090/gmap.html. The console should readout any tweets, as well as updating the actual twitter at https://twitter.com/FlightsOverRose . Whenever a plane passes overhead, the buzzer will beep and the twitter account will update with the new information.<br />
<br />
== Highlights ==<br />
<br />
(Here is where you brag about what your project can do.<br />
Include a [http://www.youtube.com/ YouTube] demo.)<br />
<br />
== Theory of Operation ==<br />
<br />
The utility dump1090 calibrates and begins the SDR's collection of data. The script begindump.sh starts this process and starts dump1090 with the option to deposit all data gathered into a .json file ./dump1090/public_html/data/aircraft.json. Using the script ./HTMLserver.sh, a basic python html server is started on port 8090 that views that data in an html form.<br />
<br />
For my project, the same aircraft.json file that serves the html page is queried and used to compile data on the local flights. The program ./listPlanes.py gathers this data and filters out the planes that don't have a strong enough signal to give specific aircraft information such as flight number or speed. If this information is present, each plane and its values are recorded, and the distance to each plane from the local position (currently assume to be Rose-Hulman in Terre Haute, IN) is calculated using geopy's vincety distance between two points in the form (latitude, longitude). This program was the first step in processing the information used in the project, and can currently be used to check the distance to each fully visible plane.<br />
<br />
In ./tweetPlanes.py, ./listPlanes.py has been expanded to include the functionality to tweet and activate a buzzer to inform the user whenever a plane is close enough to be locally seen. The distance is set to 20 miles by default, and whenever a plane is detected within this distance, a tweet including its flight number, distance, speed, altitude, and a link to a third party flight-tracker is included in the tweet. The twitter feed operates through use of the utility tweepy, which integrates with a custom-made application on apps.twitter.com, communicating via public and private keys to the twitter account.<br />
<br />
== Work Breakdown ==<br />
<br />
Installed dump1090 - 10/22/17<br />
<br />
Tested dump1090 -10/22/17<br />
<br />
Installed dump978 - 10/29/17<br />
<br />
Tested dump978 - 10/29/17<br />
<br />
Analyze dump1090 source - 11/2/17<br />
<br />
Create listPlanes.py program - 11/5/17<br />
<br />
Finish implementation of listPlanes.py - 11/6/17<br />
<br />
Create tweetPlanes.py - 11/7/17<br />
<br />
Finish implementation of tweetPlanes.py 11/10/17<br />
<br />
Finish documentation on wiki - 11/13/17<br />
<br />
== Future Work == <br />
<br />
A great deal of time was spent trying to integrate planes from the 978 MHz band using another utility dump978, but the information was presented in a different manner that I found difficult to integrate into the project. This is possible however, and would expand the usefulness of the tool.<br />
<br />
More information from the flight, such as flight origin and destination could be included.<br />
<br />
Weather information could be pulled from an open API, and visibility information could be used to make sure all planes that trigger an alert are actually in the seeable range.<br />
<br />
== Conclusions ==<br />
<br />
<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=456281ECE497 Project: Local Air Traffic Radio2017-11-14T12:43:15Z<p>Bretscak: updated theory of operation</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
RTL-SDR radios can monitor local air traffic via ADS-B signals. These signals include much information about the flight, including latitude, longitude, height and other flight charactertics.<br />
<br />
Currently the utility dump1090 can output plane data to a html page. This page shows the direction and location of each plane in sensor range, but is only accessible in the local network.<br />
<br />
The goal of this project is to create a device that will track the local air traffic and alert the user whenever a plane comes close enough to look out the window and see<br />
<br />
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 to see. These planes will be found using the dump1090 utility and the system will alert the user via both a buzzer and by tweeting the plane's information<br />
== Packaging ==<br />
Components used are listed below:<br />
<br />
BeagleBone Blue:<br />
https://beagleboard.org/blue<br />
<br />
Software Defined Radio:<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
Electronic Buzzer:<br />
https://www.adafruit.com/product/1536<br />
<br />
== Installation Instructions ==<br />
<br />
https://github.com/AdamBretsch/SDRFlights<br />
See README.md in github directory.<br />
<br />
Current sources:<br />
<br />
https://randomkeystrokes.com/2016/07/02/installing-dump1090-adsb-decoder-tool-on-ubuntu-16-04-lts/<br />
https://github.com/antirez/dump1090<br />
<br />
(* 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]. <br />
* 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.<br />
* Include a Makefile for you code.<br />
* Include any additional packages installed via '''apt'''.<br />
* Include kernel mods.<br />
* If there is extra hardware needed, include links to where it can be obtained.)<br />
<br />
== User Instructions ==<br />
<br />
(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.)<br />
<br />
== Highlights ==<br />
<br />
(Here is where you brag about what your project can do.<br />
Include a [http://www.youtube.com/ YouTube] demo.)<br />
<br />
== Theory of Operation ==<br />
<br />
The utility dump1090 calibrates and begins the SDR's collection of data. The script begindump.sh starts this process and starts dump1090 with the option to deposit all data gathered into a .json file ./dump1090/public_html/data/aircraft.json. Using the script ./HTMLserver.sh, a basic python html server is started on port 8090 that views that data in an html form.<br />
<br />
For my project, the same aircraft.json file that serves the html page is queried and used to compile data on the local flights. The program ./listPlanes.py gathers this data and filters out the planes that don't have a strong enough signal to give specific aircraft information such as flight number or speed. If this information is present, each plane and its values are recorded, and the distance to each plane from the local position (currently assume to be Rose-Hulman in Terre Haute, IN) is calculated using geopy's vincety distance between two points in the form (latitude, longitude). This program was the first step in processing the information used in the project, and can currently be used to check the distance to each fully visible plane.<br />
<br />
In ./tweetPlanes.py, ./listPlanes.py has been expanded to include the functionality to tweet and activate a buzzer to inform the user whenever a plane is close enough to be locally seen. The distance is set to 20 miles by default, and whenever a plane is detected within this distance, a tweet including its flight number, distance, speed, altitude, and a link to a third party flight-tracker is included in the tweet. The twitter feed operates through use of the utility tweepy, which integrates with a custom-made application on apps.twitter.com, communicating via public and private keys to the twitter account.<br />
<br />
== Work Breakdown ==<br />
<br />
Done:<br />
Installed dump1090 - 10/22/17<br />
Tested dump1090 -10/22/17<br />
Installed dump978 - 10/29/17<br />
Tested dump978 - 10/29/17<br />
<br />
To be done:<br />
Analyze dump1090 source - 11/2/17<br />
Analyze dump978 source - 11/2/17<br />
Combine code dump 1090 and dump978 - 11/7/17<br />
Combine display outputs - 11/3/17<br />
<br />
== Future Work == <br />
<br />
Could add twitter interface to send alerts over the Internet.<br />
<br />
== Conclusions ==<br />
<br />
<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=454271ECE497 Project: Local Air Traffic Radio2017-10-31T15:00:16Z<p>Bretscak: corrected format error</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Packaging ==<br />
BeagleBone Blue:<br />
<br />
https://beagleboard.org/blue<br />
<br />
Currently using these SDRs:<br />
<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
http://www.nooelec.com/store/sdr/nesdr-smart-xtr.html<br />
<br />
<br />
(consider [http://cpprojects.blogspot.com/2013/07/small-build-big-execuition.html Small Build, Big Execuition] for ideas on the final packaging)<br />
<br />
== Installation Instructions ==<br />
<br />
Current sources:<br />
<br />
https://randomkeystrokes.com/2016/07/02/installing-dump1090-adsb-decoder-tool-on-ubuntu-16-04-lts/<br />
https://github.com/antirez/dump1090<br />
<br />
(* 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]. <br />
* 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.<br />
* Include a Makefile for you code.<br />
* Include any additional packages installed via '''apt'''.<br />
* Include kernel mods.<br />
* If there is extra hardware needed, include links to where it can be obtained.)<br />
<br />
== User Instructions ==<br />
<br />
(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.)<br />
<br />
== Highlights ==<br />
<br />
(Here is where you brag about what your project can do.<br />
Include a [http://www.youtube.com/ YouTube] demo.)<br />
<br />
== Theory of Operation ==<br />
<br />
Dump1090 and dump978 are seperate programs that us a RTL-SDR usb dongle to look at a band of air traffic radio. The software will combine the outputs of these two radios into a new utility that combines both and identifies them. This display will show the different bands as different colors.<br />
<br />
Whenever a plane is detected close enough to the radios, a buzzer or alarm will go of as an alert. This is so you can find the planes in the sky, or identify planes from a nearby air traffic.<br />
<br />
== Work Breakdown ==<br />
<br />
Done:<br />
Installed dump1090 - 10/22/17<br />
Tested dump1090 -10/22/17<br />
Installed dump978 - 10/29/17<br />
Tested dump978 - 10/29/17<br />
<br />
To be done:<br />
Analyze dump1090 source - 11/2/17<br />
Analyze dump978 source - 11/2/17<br />
Combine code dump 1090 and dump978 - 11/7/17<br />
Combine display outputs - 11/3/17<br />
<br />
== Future Work == <br />
<br />
Could add twitter interface to send alerts over the Internet.<br />
<br />
== Conclusions ==<br />
<br />
<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=454266ECE497 Project: Local Air Traffic Radio2017-10-31T14:59:11Z<p>Bretscak: added basic information</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Executive Summary ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Packaging ==<br />
BeagleBone Blue:<br />
<br />
https://beagleboard.org/blue<br />
<br />
Currently using these SDRs:<br />
<br />
https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/<br />
<br />
http://www.nooelec.com/store/sdr/nesdr-smart-xtr.html<br />
<br />
<br />
(consider [http://cpprojects.blogspot.com/2013/07/small-build-big-execuition.html Small Build, Big Execuition] for ideas on the final packaging)<br />
<br />
== Installation Instructions ==<br />
<br />
Current sources:<br />
<br />
https://randomkeystrokes.com/2016/07/02/installing-dump1090-adsb-decoder-tool-on-ubuntu-16-04-lts/<br />
https://github.com/antirez/dump1090<br />
<br />
(* 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]. <br />
* 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.<br />
* Include a Makefile for you code.<br />
* Include any additional packages installed via '''apt'''.<br />
* Include kernel mods.<br />
* If there is extra hardware needed, include links to where it can be obtained.)<br />
<br />
== User Instructions ==<br />
<br />
(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.)<br />
<br />
== Highlights ==<br />
<br />
(Here is where you brag about what your project can do.<br />
Include a [http://www.youtube.com/ YouTube] demo.)<br />
<br />
== Theory of Operation ==<br />
<br />
Dump1090 and dump978 are seperate programs that us a RTL-SDR usb dongle to look at a band of air traffic radio. The software will combine the outputs of these two radios into a new utility that combines both and identifies them. This display will show the different bands as different colors.<br />
<br />
Whenever a plane is detected close enough to the radios, a buzzer or alarm will go of as an alert. This is so you can find the planes in the sky, or identify planes from a nearby air traffic.<br />
<br />
== Work Breakdown ==<br />
<br />
Done:<br />
Installed dump1090 - 10/22/17<br />
Tested dump1090 -10/22/17<br />
Installed dump978 - 10/29/17<br />
Tested dump978 - 10/29/17<br />
<br />
To be done:<br />
Analyze dump1090 source - 11/2/17<br />
Analyze dump978 source - 11/2/17<br />
Combine code dump 1090 and dump978 - 11/7/17<br />
Combine display outputs - 11/3/17<br />
<br />
== Future Work == <br />
<br />
Could add twitter interface to send alerts over the Internet.<br />
<br />
== Conclusions ==<br />
<br />
<br />
== Grading ==<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: <br />
Score: /100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span></div>Bretscakhttps://elinux.org/index.php?title=ECE497_Project:_Local_Air_Traffic_Radio&diff=454186ECE497 Project: Local Air Traffic Radio2017-10-31T12:54:23Z<p>Bretscak: created new project page</p>
<hr />
<div>[[Category:ECE497 |PL]]<br />
<br />
Team members: [[user:bretscak|Adam Bretsch]]<br />
<br />
== Grading Template ==<br />
I'm using the following template to grade. Each slot is 10 points.<br />
0 = Missing, 5=OK, 10=Wow!<br />
<br />
<pre style="color:red"><br />
00 Executive Summary<br />
00 Installation Instructions <br />
00 User Instructions<br />
00 Highlights<br />
00 Theory of Operation<br />
00 Work Breakdown<br />
00 Future Work<br />
00 Conclusions<br />
00 Demo<br />
00 Late<br />
Comments: I'm looking forward to seeing this.<br />
<br />
Score: 10/100<br />
</pre><br />
<br />
<span style="color:red">(Inline Comment)</span><br />
<br />
== Executive Summary ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Packaging ==<br />
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.<br />
<br />
== Installation Instructions ==<br />
<br />
Give step by step instructions on how to install your project. <br />
<br />
* 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]. <br />
* 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.<br />
* Include a Makefile for you code.<br />
* Include any additional packages installed via '''apt'''.<br />
* Include kernel mods.<br />
* If there is extra hardware needed, include links to where it can be obtained.<br />
<br />
== User Instructions ==<br />
<br />
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.<br />
<br />
== Highlights ==<br />
<br />
Here is where you brag about what your project can do.<br />
<br />
Include a [http://www.youtube.com/ YouTube] demo.<br />
<br />
== Theory of Operation ==<br />
<br />
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.<br />
<br />
== Work Breakdown ==<br />
<br />
List the major tasks in your project and who did what.<br />
<br />
Also list here what doesn't work yet and when you think it will be finished and who is finishing it.<br />
<br />
== Future Work ==<br />
<br />
Suggest addition things that could be done with this project.<br />
<br />
== Conclusions ==<br />
<br />
Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.</div>Bretscakhttps://elinux.org/index.php?title=EBC_Exercise_01_Start_Here&diff=450136EBC Exercise 01 Start Here2017-09-01T01:33:01Z<p>Bretscak: Corrected color error</p>
<hr />
<div>[[Category:ECE497]]<br />
{{YoderHead}}<br />
<br />
== Overview ==<br />
<br />
There are three major things that need to be done to have the BeagleBoard ready to run for class:<br />
# Get your Beagle Hardware together<br />
# Set up a host computer, running Linux for code development<br />
# Clone the course git repository on both the host and the Beagle<br />
<br />
== The Hardware ==<br />
<br />
Here's the hardware you will need and where you get it.<br />
<br />
=== You may have, or will have to buy ===<br />
<br />
We are using the [http://beagleboard.org/blue BeagleBone Blue] this year. Since it's only $50 (or so) I'll have you buy your own. There are a few other things you will need to get before the first day of class.<br />
* BeagleBone Blue. See [http://beagleboard.org/blue http://beagleboard.org/blue] for suggestions of where to buy the Blue. I suggest ordering sooner rather than later since it may take a couple of weeks. <br />
* At least two 8G micro SD cards. I suggest you have 2 or 3 cards since it's easy to mess up one and it takes some 10 minutes to reload it.<br />
* micro SD card reader/writer<br />
* Powered USB hub, at least 4 ports. The Blue has only one USB port so this will allow you to plug in the keyboard, mouse, web cam, etc.<br />
<br />
==== Books ====<br />
* [http://shop.oreilly.com/product/0636920033899.do BeagleBone Cookbook] (Not the BeagleBone Black Cookbook, it's a different book.)<br />
* (optional but good) [http://exploringbeaglebone.com/ Exploring BeagleBone].<br />
<br />
=== What you buy from the Instrument Room ===<br />
<br />
* various input devices, sensors, displays, etc.<br />
<br />
=== What you borrow from the Instrument Room ===<br />
* Proto Plate with full sized breadboard<br />
* 5V power supply<br />
* [http://us.playstation.com/ps3/accessories/playstation-eye-camera-ps3.html Playstation EYE] web cam<br />
* [http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10419&cs_id=1041913&p_id=7703&seq=1&format=2 micro HDMI to HDMI adapter]<br />
* [https://www.sparkfun.com/products/9717 FTDI USB to Serial Adapter] Must be 3.3V version<br />
* [http://www.adafruit.com/products/902 Bicolor LED Square Pixel Matrix with I2C Backpack]<br />
* Two (2) [http://www.ti.com/product/tmp101 TMP101] temperature sensors<br />
* [http://www.ti.com/product/tmp006 TMP006] Infrared Thermopile Sensor (too small to mount, we won't use this)<br />
* [http://www.ti.com/product/pca9306 PCA9306 Dual Bi-Directional I2C-Bus and SMBus Voltage Level-Translator]<br />
* [http://www.ti.com/product/l293 L293 Quadruple Half-H Drivers]<br />
<br />
== The Linux host computer ==<br />
<br />
The above will get you ready for about the first 4 weeks of class. Around week 5 we'll start looking at the kernel and will need to cross compile. Once we start moving into Kernel development we will need a host computer. Since we are doing Linux development, it's generally agreed the host should be running Linux. I suggest you run [http://www.ubuntu.com Ubuntu 16.04 (LTS)]. The CSSE department has a [ftp://ftp.csse.rose-hulman.edu/ubuntu-releases/16.04 local copy] you can access on campus, so you don't have to download some 700M from elsewhere. You want the '''desktop-amd64.iso''' if you have a 64-bit machine, or the '''desktop-i386.iso''' if you are running 32-bits.<br />
<br />
There are three options as to how to run Linux.<br />
# Native install ([http://www.ubuntu.com/download])<br />
# Install in a virtual machine. I've been running [[EBC Exercise 06 Notes on VirtualBox | Virtual Box]] recently and it works fine. I suggest using it. You can also try [[EBC_Exercise_07_Installing_Ubuntu_in_VMware | VMware Player]] if you would like.<br />
# Run in the cloud<br />
<br />
No matter which method you use be sure to have some 30G of disk space. The kernel tools will need at least 6G.<br />
<br />
The Ubuntu site gives good instructions for a native install. I've had good success with running both VMware and Virtual Box, though my installation instructions are a bit dated. (Feel free to update them if they need it.)<br />
<br />
I've been testing out the "Cloud" approach and it looks like it will work too. If you want to try the cloud, let me known and I'll show you how.<br />
<br />
<br />
{{YoderHead}}</div>Bretscakhttps://elinux.org/index.php?title=EBC_Editing_a_Wiki&diff=450131EBC Editing a Wiki2017-09-01T00:55:05Z<p>Bretscak: Added my name to edit list</p>
<hr />
<div>[[Category:ECE597 |exer12]]<br />
{{YoderHead}}<br />
<br />
Here is a wiki you can practice editing. Before you can edit it you will have to create an login. Pick something that will make it easy for me to identify you as part of my class. Then just add your name and date on the end of the table.<br />
<br />
You can get help here: [[Help:Contents]].<br />
<br />
If you need help with syntax check out the [[Editing Quickstart Guide|eLinux guide]] or the [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wikipedia Cheatsheet].<br />
<br />
==Fall 2017 ==<br />
{|<br />
| [[user:Bretscak | Adam Bretsch]] <br />
| 31-Aug-2017<br />
|-<br />
|}<br />
{|<br />
| [[user:SaraHB | Sara Harvey-Browne]] <br />
| 31-Aug-2017<br />
|-<br />
|}<br />
{|<br />
|[[user:Daniel.Neelappa | Daniel Neelappa]] <br />
| 31-Aug-2017<br />
|-<br />
|}<br />
<br />
== Fall 2016 ==<br />
{|<br />
| [[user:davidcaggiano | David J. Caggiano]]<br />
| 1-Sep-2016<br />
|-<br />
| [[user:Koontz | Alvin Koontz]]<br />
| 2-Sep-2016<br />
|-<br />
| [[user:Gfrung4 | George F. Rung]]<br />
| 2-Sep-2016<br />
|-<br />
| [[user:Smithtl | Tim L. Smith]]<br />
| 2-Sep-2016<br />
|}<br />
<br />
== Fall 2015 ==<br />
<br />
{|<br />
| [[user:yoder | Mark A. Yoder]]<br />
| 10-Aug-2015<br />
|-<br />
| [[user:DivakarMaurya | Divakar Maurya]]<br />
| 16-Sep-2015<br />
|-<br />
| [[user:Rajat Valecha | Rajat Valecha]]<br />
| 16-Aug-2015<br />
|-<br />
| [[user:ahmed | Ahmed Karanath]]<br />
| 13-Aug-2015<br />
|-<br />
| [[user:Himanshu Kamboj| Himanshu Kamboj]]<br />
| 16-Sept-2015<br />
|-<br />
| [[user:gopalkriagg | Gopal Krishan Aggarwal]]<br />
| 12-Aug-2015<br />
|-<br />
| [[user:vishalgoel003 | Vishal Goel]]<br />
| 11-Aug-2015<br />
|-<br />
| [[user:Tshrjn | Tushar Jain]]<br />
| 10-Sept-2015<br />
|-<br />
| [[user:Anand K. Parmar | Anand K. Parmar]]<br />
| 10-Aug-2015<br />
|-<br />
| [[user:Mohit sharma | Mohit sharma]]<br />
| 31-Aug-2015<br />
|-<br />
| [[user:sanjeev_k | Sanjeev Khare]]<br />
| 15-Aug-2015<br />
|-<br />
| [[user:kanz | Kansul Mahrifa]]<br />
| 19-Aug-2015<br />
|-<br />
| [[user:manojkumar | Manoj Kumar]]<br />
| 19-Aug-2015<br />
|- <br />
| [[user:sadwith gogula | Sadwith gogula]]<br />
| 19-Aug-2015<br />
|-<br />
| [[user:pkm619 | Pushpendra kumar]]<br />
| 20-Aug-2015<br />
|-<br />
| [[user:guntukuvikas | Guntuku Vikas]]<br />
| 25-Aug-2015<br />
|-<br />
| [[user:sidgangal | Siddharth Gangal]]<br />
| 25-Aug-2015<br />
|-<br />
| [[user:Roby1234 | Onkar Singh]]<br />
| 25-Aug-2015<br />
|-<br />
| [[user:vinodkgupta | vinod kumar]]<br />
| 25-Aug-2015<br />
|-<br />
| [[user:merlin sundar | Merlin sundar]]<br />
| 25-Aug-2015<br />
|}<br />
<br />
== Fall 2014 ==<br />
<br />
{|<br />
| [[user:yoder | Mark A. Yoder]]<br />
| 6-Aug-2014<br />
|-<br />
| [[user:JiayuGuo | Jiayu Guo]]<br />
| 25-sep-2014<br />
|-<br />
| [[user:zwj102030 | Weijian zhang]]<br />
| 18-sep-2014<br />
|-<br />
<br />
| [[user:XHa0z | Zhihao Xue]]<br />
| 4-Sept-2014<br />
|-<br />
| [[user:caiocvsilva | Caio Silva]]<br />
| 5-Sept-2014<br />
|-<br />
| [[user:MattOlson | Matt Olson]]<br />
| 7-Sept-2014<br />
|-<br />
| [[user:Leihao | Leihao Wei]]<br />
| 7-Sept-2014<br />
|-<br />
| [[user:Mikuzz | Zizhao Wang]]<br />
| 7-Sept-2014<br />
|-<br />
|[[user:Zhouy | Ying Ying Zhou]]<br />
| 7-Sept-2014<br />
|-<br />
|[[user:Eric Taylor | Eric Taylor]]<br />
| 7-Sept-2014<br />
|-<br />
|[[user:Peter_Olejnik | Peter Olejnik]]<br />
| 7-Sept-2014<br />
|-<br />
|[[user:Dmitryvv | Dmitry Votintsev]]<br />
| 7-Sept-2014<br />
|-<br />
|[[user:morrisma| Mark Morrison]]<br />
| 9-Sept-2014<br />
|-<br />
|[[user:vaddera| Alexandre van der Ven de Freitas]]<br />
| 9-Sept-2014<br />
|-<br />
|[[user:randallsturner13| Randy Turner]]<br />
| 11-Sept-2014<br />
|-<br />
|[[user:ADraicBrom| Asa Bromenschenkel]]<br />
| 18-Sept-2014<br />
|-<br />
|}<br />
<br />
== Winter 2013 ==<br />
{|<br />
|-<br />
| [[user:cattnb | Nathan Catt]]<br />
| 28-November-2013<br />
|-<br />
| [[user:belkat | Andrew Belk]]<br />
| 7 Dec 2013<br />
|-<br />
|}<br />
<br />
== Fall 2013 ==<br />
<br />
{|<br />
|-<br />
| [[user:amesen | Eric Ames]]<br />
| 13-June-2013<br />
|-<br />
| [[user:fendrirj | Robert Fendricks]]<br />
| 5-September-2013<br />
|-<br />
| [[user:elswicwj | Will Elswick]]<br />
| 5-September-2013<br />
|-<br />
| [[user:savrdada | David Savrda]]<br />
| 5-September-2013<br />
|-<br />
| [[user:skorinm | Matt Skorina]]<br />
| 6-September-2013<br />
|-<br />
| [[user:Parasby | Ben Paras]]<br />
| 6-September-2013<br />
|-<br />
| [[user:Yuxuan | Yuxuan Zeng]]<br />
| 5-September-2013<br />
|-<br />
| [[user:Mcdonamp | Mike McDonald]]<br />
| 5-September-2013<br />
|-<br />
| [[user:Kowalsif | Ian Kowalski]]<br />
| 5-September-2013<br />
|-<br />
| [[user:daniel.hou | Junxuan Hou]]<br />
| 5-September-2013<br />
|-<br />
| [[user:Andrewca | Chris Andrews]]<br />
| 5-September-2013<br />
|-<br />
| [[user:Rockybulwinkle | Chris Hopwood]]<br />
| 6-September-2013<br />
|-<br />
| [[user:Tpurviance | Taylor Purviance]]<br />
| 6-September-2013<br />
|-<br />
| [[user:Manuel | Manuel Stephan]]<br />
| 8-September-2013<br />
|-<br />
| [[user:FreeTymeKiyan | Yang Liu]]<br />
| 8-September-2013<br />
|-<br />
| [[user:Cooperdl | David Cooper]]<br />
| 9-September-2013<br />
|-<br />
| [[user:Alvareap | Alex Alvarez]]<br />
| 10-September-2013<br />
|-<br />
|}<br />
<br />
== Fall 2012 ==<br />
<br />
{|<br />
|-<br />
| [[user:Yoder | Mark A. Yoder]]<br />
| 18-July-2012<br />
|-<br />
| [[user:atniptw | Tom Atnip]]<br />
| 20-July-2012<br />
|-<br />
| [[user:Xinyu1991 | Xinyu Cheng]]<br />
| 31-August-2012<br />
|-<br />
| [[user:bssachin45 | B S Sachin]]<br />
| 25-July-2012<br />
|-<br />
| [[user:ruff | Ruffin White]]<br />
| 16-August-2012<br />
|-<br />
| [[user:Popenhjc | James Popenhagen]]<br />
| 30-August-2012<br />
|-<br />
| [[user:mmoravec | Matthew Moravec]]<br />
| 30-August-2012<br />
|-<br />
| [[user:ngop | Peter Ngo]]<br />
| 30-August-2012<br />
|-<br />
| [[user:duganje | Josh Dugan]]<br />
| 30-August-2012<br />
|-<br />
| [[user:hansenrl | Ross Hansen]]<br />
| 30-August-2012<br />
|-<br />
| [[user:jungeml | Michael Junge]]<br />
| 05-September-2012<br />
|- <br />
| [[User:shinnsm|Stephen Shinn]]<br />
| 30-August-2012<br />
|-<br />
| [[User:draneaw|Alex Drane]]<br />
| 30-August-2012<br />
|-<br />
| [[User:larmorgs|Greg Larmore]]<br />
| 31-August-2012<br />
|-<br />
| [[User:jessebrannon|Jesse Brannon]]<br />
| 31-August-2012<br />
|-<br />
| [[User:lix|Xia Li]]<br />
| 31-August-2012<br />
|-<br />
| [[User:whiteer|Elias White]]<br />
| 31-August-2012<br />
|-<br />
| [[User:Astroricks|Yue Zhang]]<br />
| 31-August-2012<br />
|-<br />
| [[User:millerap|Andrew Miller]]<br />
| 31-August-2012<br />
|-<br />
| [[user:Geislekj | Kevin Geisler]]<br />
| 1-September-2012<br />
|-<br />
| [[user:chris.good | Christopher A Good]]<br />
| 3-September-2012<br />
|-<br />
| [[user:Lobdeljt | John Lobdell]]<br />
| 5-November-2012<br />
|}<br />
<br />
== Winter 2011-2012 ==<br />
<br />
{|<br />
|-<br />
| [[user:Yoder | Mark A. Yoder]]<br />
| 21-Nov-2011<br />
|-<br />
| [[user:Yuming | Yuming Cao]]<br />
| 21-Nov-2011<br />
|-<br />
| [[user:Yuhasmj | Michael Yuhas]]<br />
| 21-Nov-2011<br />
|-<br />
| [[user:Yifei | Yifei Li]]<br />
| 22-Nov-2011<br />
|-<br />
| [[user:Ziyi Zhang | Ziyi Zhang]]<br />
| 24-Nov-2011<br />
|-<br />
|[[user: mac | Jack Ma]]<br />
| 28-Nov-2011<br />
|-<br />
| [[user:Zitnikdj | David Zitnik]]<br />
| 25-Nov-2011<br />
|-<br />
| [[user:Harrisgw | Greg Harrison]]<br />
| 26-Nov-2011<br />
|-<br />
| [[user:Yanj | Mona J Yan]]<br />
| 27-Nov-2011<br />
|-<br />
| [[user:Gemini91 | Guanqun Wang]]<br />
| 28-Nov-2011<br />
|-<br />
| [[user:vsn1985 | Narayanan VS]]<br />
| 28-Nov-2011<br />
|}<br />
<br />
<br />
{{YoderFoot}}</div>Bretscakhttps://elinux.org/index.php?title=User:Bretscak&diff=450126User:Bretscak2017-09-01T00:53:42Z<p>Bretscak: Added clarification of class</p>
<hr />
<div>[[Category:ECE497 |UB]]</div>Bretscak