FlightAware - Revision history

Unknown user: /* Install dump1090-fa */

2020-08-17T20:33:12Z

Install dump1090-fa

← Older revision		Revision as of 20:33, 17 August 2020
Line 80:		Line 80:
	</pre>		</pre>

	You DO NOT want to build this manually - that will cause dump1090 binaries to sit in that directory and they will not be found on your path. Furthermore, there will be no startup service, and the piaware program tries to invoke dump1090-fa via a startup service. ~~(Also see:~~ So, just build the .deb package. (If you see warnings about not being able to sign the package with a GPG key, that's okay, we're just building the package for ourselves.)		You DO NOT want to build this manually - that will cause dump1090 binaries to sit in that directory and they will not be found on your path. Furthermore, there will be no startup service, and the piaware program tries to invoke dump1090-fa via a startup service. So, just build the .deb package. (If you see warnings about not being able to sign the package with a GPG key, that's okay, we're just building the package for ourselves.)

	<pre>		<pre>

Admin: /* Software/Installation */

2017-08-23T00:05:19Z

Software/Installation

← Older revision		Revision as of 00:05, 23 August 2017
Line 15:		Line 15:
	In the end you will have software receiving signals from aircraft transponders, decoding the information, displaying it in a dashboard, and forwarding it on to FlightAware.		In the end you will have software receiving signals from aircraft transponders, decoding the information, displaying it in a dashboard, and forwarding it on to FlightAware.

	[[Image:~~FlightStatsLocal~~.png\|500px]]		[[Image:FlightStatsLocal2.png\|500px]]

	===Install software needed===		===Install software needed===

Admin: /* Software/Installation */

2017-08-22T13:38:11Z

Software/Installation

← Older revision		Revision as of 13:38, 22 August 2017
Line 12:		Line 12:

	Scripts to execute the commands below can be downloaded here: https://git.charlesreid1.com/charlesreid1/flight-aware		Scripts to execute the commands below can be downloaded here: https://git.charlesreid1.com/charlesreid1/flight-aware

			In the end you will have software receiving signals from aircraft transponders, decoding the information, displaying it in a dashboard, and forwarding it on to FlightAware.

			[[Image:FlightStatsLocal.png\|500px]]

	===Install software needed===		===Install software needed===

Admin: /* Flight Stats Page */

2017-08-22T13:37:28Z

Flight Stats Page

← Older revision		Revision as of 13:37, 22 August 2017
Line 172:		Line 172:
	See [[#Troubleshooting]] section below for expected output.		See [[#Troubleshooting]] section below for expected output.

	===Flight Stats Page===		===FlightAware Flight Stats Page===

	~~There are two~~ FlightAware ~~stats pages:~~		To submit information to FlightAware, you need a FlightAware username. FlightAware keeps track of the statics that you have submitted to their site. The stats page for a given FlightAware receiver requires an internet connection, and can be found by inserting your username in the following URL: <code><nowiki>http://flightaware.com/adsb/stats/user/<username></nowiki></code>.
	* FlightAware stats page (requires internet connection, ~~up to 2 minute delay)~~
	* Local FlightAware stats ~~page~~

	~~The remote~~ FlightAware stats page ~~can be found by inserting your username in the following~~ URL: ~~<code><nowiki>~~http://flightaware.com/adsb/stats/user/~~<username></nowiki></code>.~~		For example, here's my FlightAware stats page URL: http://flightaware.com/adsb/stats/user/charlesreid1

	~~For example, here's my FlightAware stats page URL: http://flightaware.com/adsb/stats/user/charlesreid1~~		===Skyview Local Stats Page===

	~~The second (~~local) stats page requires the lighttpd service to be running. ~~This~~ should be installed as part of the FlightAware prerequisite software installation step. From the machine running the FlightAware software, start the lighttpd service:		Alternatively, there is a local stats page (Skyview), which requires the lighttpd service to be running. It does not require an internet connection, but without an internet connection you will not see a map. The lighttpd service should have been installed as part of the FlightAware prerequisite software installation step. From the machine running the FlightAware software, start the lighttpd service:

	<pre>		<pre>

Admin: /* Flight Stats Page */

2017-08-22T13:23:55Z

Flight Stats Page

← Older revision		Revision as of 13:23, 22 August 2017
Line 174:		Line 174:
	===Flight Stats Page===		===Flight Stats Page===

	There are two FlightAware stats pages: ~~the first one~~ requires an internet connection, ~~and has an~~ up to 2 minute delay~~. The second runs locally, and shows~~ stats ~~on planes spotted locally by the FlightAware/PiAware device.~~		There are two FlightAware stats pages:
			* FlightAware stats page (requires internet connection, up to 2 minute delay)
			* Local FlightAware stats page

			The remote FlightAware stats page can be found by inserting your username in the following URL: <code><nowiki>http://flightaware.com/adsb/stats/user/<username></nowiki></code>.

	~~To find the first one, you'll need to sign up for a FlightAware account. Then use your username in the following URL: <code><nowiki>http://flightaware.com/adsb/stats/user/<username></nowiki></code>.~~ For example, here's my FlightAware stats page URL: http://flightaware.com/adsb/stats/user/charlesreid1		For example, here's my FlightAware stats page URL: http://flightaware.com/adsb/stats/user/charlesreid1

	The second ~~page, the~~ local stats page~~, can~~ be ~~found at port 8080 on the machine~~ running the FlightAware software. From the machine running the FlightAware software, visit localhost:8080; from ~~another~~ machine ~~on the same local network~~, ~~visit~~ 192.168.X.Y:8080 (~~or whatever~~ the IP address of the machine running FlightAware is).		The second (local) stats page requires the lighttpd service to be running. This should be installed as part of the FlightAware prerequisite software installation step. From the machine running the FlightAware software, start the lighttpd service:

			<pre>
			$ service lighttpd start
			</pre>

			This should open port 8080. Next, visit localhost:8080 from that machine, or 192.168.X.Y:8080 (use the IP address of the machine running FlightAware) to connect to the page over the local network. You should see a page like the screenshot below. If you get a 404 or a page not found, make sure the lighttpd service is running.

			[[Image:FlightStatsLocal.png\|500px]]

	==Troubleshooting==		==Troubleshooting==

Admin: /* Flags */

2017-08-22T11:59:12Z

Flags

← Older revision		Revision as of 11:59, 22 August 2017
Line 295:		Line 295:

	==Flags==		==Flags==

			{{SDRFlag}}

			{{RadioFlag}}


	[[Category:Radio]]		[[Category:Radio]]
	[[Category:SDR]]		[[Category:SDR]]

Admin: /* Running */

2017-08-22T05:22:09Z

Running

← Older revision		Revision as of 05:22, 22 August 2017
Line 154:		Line 154:

	==Running==		==Running==

			===Start Dump1090 Startup Service===

	Once you've run through each of the steps above, you can run piaware by first starting the dump1090-fa startup service, then starting the piaware startup service:		Once you've run through each of the steps above, you can run piaware by first starting the dump1090-fa startup service, then starting the piaware startup service:
Line 168:		Line 170:
	</pre>		</pre>

	~~Output~~:		See [[#Troubleshooting]] section below for expected output.

			===Flight Stats Page===

			There are two FlightAware stats pages: the first one requires an internet connection, and has an up to 2 minute delay. The second runs locally, and shows stats on planes spotted locally by the FlightAware/PiAware device.


			To find the first one, you'll need to sign up for a FlightAware account. Then use your username in the following URL: <code><nowiki>http://flightaware.com/adsb/stats/user/<username></nowiki></code>. For example, here's my FlightAware stats page URL: http://flightaware.com/adsb/stats/user/charlesreid1

	~~[[Image~~:~~SystemctlStatusPiawareSuccess~~.~~png\|500px]]~~		The second page, the local stats page, can be found at port 8080 on the machine running the FlightAware software. From the machine running the FlightAware software, visit localhost:8080; from another machine on the same local network, visit 192.168.X.Y:8080 (or whatever the IP address of the machine running FlightAware is).

	==Troubleshooting==		==Troubleshooting==

Admin: /* Checking Status: Method 1 */

2017-08-22T05:16:55Z

Checking Status: Method 1

← Older revision		Revision as of 05:16, 22 August 2017
Line 177:		Line 177:

	To check on the status of piaware, and assuming it was installed using the piaware_builder repository (i.e., that you built a debian package and installed it using dpkg), which also creates a startup service, you can use systemctl to check on the status of the startup service:		To check on the status of piaware, and assuming it was installed using the piaware_builder repository (i.e., that you built a debian package and installed it using dpkg), which also creates a startup service, you can use systemctl to check on the status of the startup service:

			Output:

			[[Image:SystemctlStatusPiawareSuccess.png\|500px]]

	<pre>		<pre>

Admin: /* Install dump1090-fa */

2017-08-19T00:08:02Z

Install dump1090-fa

← Older revision		Revision as of 00:08, 19 August 2017
Line 66:		Line 66:
	===Install dump1090-fa===		===Install dump1090-fa===

	Next install ~~software specifically for~~ dump1090-fa. At the conclusion of this step, you should be able to see your first flight information from the receiver.		Next, we need to install a program to dump out (and decode) information from the 1090 MHz band. There is a dump1090 program (generic), and there is a dump1090-fa program (specific to FlightAware). We will install dump1090-fa. At the conclusion of this step, you should be able to see your first flight information decoded from the receiver.

	Start by checkout out a copy of the flightaware dump1090 repo:		Start by checkout out a copy of the flightaware dump1090 repo:
Line 76:		Line 76:
	</pre>		</pre>

	You ~~don't~~ want to build this manually - that will cause dump1090 binaries to sit in that directory and they will not be found on your path. Furthermore, there will be no startup service, and the piaware program tries to invoke dump1090-fa via a startup service. So, just build the .deb package. (If you see warnings about not being able to sign the package with a GPG key, that's okay, we're just building the package for ourselves.)		You DO NOT want to build this manually - that will cause dump1090 binaries to sit in that directory and they will not be found on your path. Furthermore, there will be no startup service, and the piaware program tries to invoke dump1090-fa via a startup service. (Also see: So, just build the .deb package. (If you see warnings about not being able to sign the package with a GPG key, that's okay, we're just building the package for ourselves.)

	<pre>		<pre>

Admin: /* Install RTL-SDR */

2017-08-18T23:27:06Z

Install RTL-SDR

← Older revision		Revision as of 23:27, 18 August 2017
Line 43:		Line 43:

	<pre>		<pre>
	git clone git://git.osmocom.org/rtl-sdr.git ~~/root/codes/rtl-sdr~~		export RTL_DIR="/root/codes/rtl-sdr"
	cd ~~/root/codes/rtl-sdr~~		git clone git://git.osmocom.org/rtl-sdr.git ${RTL_DIR}
			cd ${RTL_DIR}
	mkdir build		mkdir build
	cd build		cd build
Line 50:		Line 51:
	make		make
	make install		make install
	~~cd /root~~		cp ${RTL_SDR}/rtl-sdr.rules /etc/udev/rules.d/.
	cp ~~/root/codes/rtl-sdr~~/rtl-sdr.rules /etc/udev/rules.d/.
	ldconfig		ldconfig