New PiAware User Cannot Get Connection to Claim w/ FlightAware, 7 Days and Frustrated


#1

So I am by no means a computer guru but I am able to get almost any technical issue sorted out with enough blogs, YouTube instructional vids, and by otherwise just hunting and poking until finding success. Well, not this time and after having been up and running at my FL home since very early this year with the FlightAware FlightFeeder box provided by them, I really have missed the level of detail I have there so I decided to move forward with putting up an antenae here at my Chicago place. Of course, they won’t offer me another one for here because coverage isn’t an issue so I paid the $200 for the PiAware prebuilt kit and have had it for over a week now and probably have spend no less than 20 hours trying to make it work, still to no avail.

When I go here:

I get this:

PiAware - Claim and Link a Brand New PiAware Ground Station

Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware feeder to claim.

FlightAware searches for PiAware connections on the same global IP (107.142.182.163) as your connection. If you are on the same LAN as the PiAware device, then we should be able to find the receiver and claim it for you. You should wait a few minutes after plugging in your PiAware device before expecting it to be connected to FlightAware. Try checking cable connections, waiting a few moments, and trying again.

If you are unable to use the automatic claim feature, please contact ADS-B Support.

Now I did call FA last week and actually what the website says is not true because they do NOT provide technical support to PiAware users or at least the nice gal I spoke to told me they do not…so here I sit and figured (as hard as it was), I need to admit my challenger and see if anyone (more the better) would be interested in accepting the challenge to provide some tips and tricks which I can use to get this site up and feeding data to FA. I was under the impression it would be easy like the box they send, but not so much the case at all.

I am all ears for all helpful suggestions, so fire away!


#2

Is your PiAware up and running and connected to FA successfully? This needs to happen before you can claim it. Do you have a monitor connected to the Pi? If so, what does it show after booting?

(Also, what do you mean by the “piaware prebuilt kit”? FA doesn’t sell these)


#3

No, it is NOT connected to FA successfully as that is the issue exactly which I’m posting about. I do have it connected to a 62" TV with mouse and keyboard so I can control very nicely from an interface perspective. I can also see that from my router, I am able to connect both via 10/100 and wirelessly as both show up as connected devices.

Correct, I purchased the following on Amazon and which I found here on the FA site as an option versus buying all of the piece parts and having to assemble myself, I purchased this:


#4

Exactly what should I show screen shots of with regards to what “what” is showing after booting as there is a lot of various programs within that little box but if you tell me precisely what you are needing I will get it to you. Thanks much I am glad I reached out for help already.


#5

Just a picture when the boot is finished.

Does it say

To access a status page and a map of nearby aircraft,
visit http://xxx.xxx.xxx.xxx from another computer on your local network.

Or is there no such message? If not it didn’t get an address from your network.

Have you visited that page? That’s actually what you want isn’t it?
Claiming it should be secondary for you.

Anyway which network is the device on? The computer you visit

Anyway you can claim your feeder with the id it shows:
Press Atl-F2 then enter this command:
sudo piaware-config -show feeder-id

Oh wait looks like you can’t enter the feeder-id manually anymore on that page?
https://flightaware.com/adsb/piaware/claim from should be on the same network.

Also pressing Alt-F10 and then snapping another picture can’t hurt.


#6

Just the final screen after it has finished booting, it should look something like this (sorry for potato camera):


#7

pi@raspberrypi:~ sudo apt-get update Get:1 http://flightaware.com jessie InRelease [1,858 B] Get:2 http://flightaware.com stretch InRelease [1,859 B] Hit http://archive.raspberrypi.org jessie InRelease Get:3 http://mirrordirector.raspbian.org jessie InRelease [14.9 kB] Get:4 http://flightaware.com jessie/piaware armhf Packages [5,877 B] Get:5 http://flightaware.com stretch/piaware armhf Packages [7,080 B] Hit http://archive.raspberrypi.org jessie/main armhf Packages Get:6 http://mirrordirector.raspbian.org jessie/main armhf Packages [9,536 kB] Hit http://archive.raspberrypi.org jessie/ui armhf Packages Ign http://flightaware.com jessie/piaware Translation-en_US Ign http://flightaware.com jessie/piaware Translation-en Ign http://archive.raspberrypi.org jessie/main Translation-en_US Ign http://archive.raspberrypi.org jessie/main Translation-en Ign http://flightaware.com stretch/piaware Translation-en_US Ign http://archive.raspberrypi.org jessie/ui Translation-en_US Ign http://archive.raspberrypi.org jessie/ui Translation-en Ign http://flightaware.com stretch/piaware Translation-en Get:7 http://mirrordirector.raspbian.org jessie/contrib armhf Packages [43.3 kB] Get:8 http://mirrordirector.raspbian.org jessie/non-free armhf Packages [84.2 kB] Get:9 http://mirrordirector.raspbian.org jessie/rpi armhf Packages [1,356 B] Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_US Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en Ign http://mirrordirector.raspbian.org jessie/main Translation-en_US Ign http://mirrordirector.raspbian.org jessie/main Translation-en Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_US Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_US Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en Fetched 9,697 kB in 22s (441 kB/s) Reading package lists... Done pi@raspberrypi:~ sudo apt-get install git
Reading package lists… Done
Building dependency tree
Reading state information… Done
Suggested packages:
git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
The following packages will be upgraded:
git
1 upgraded, 0 newly installed, 0 to remove and 362 not upgraded.
Need to get 2,736 kB of archives.
After this operation, 29.7 kB of additional disk space will be used.
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main git armhf 1:2.1.4-2.1+deb8u6 [2,736 kB]
Fetched 2,736 kB in 1s (2,372 kB/s)
Reading changelogs… Done
(Reading database … 123185 files and directories currently installed.)
Preparing to unpack …/git_1%3a2.1.4-2.1+deb8u6_armhf.deb …
Unpacking git (1:2.1.4-2.1+deb8u6) over (1:2.1.4-2.1+deb8u2) …
Setting up git (1:2.1.4-2.1+deb8u6) …
pi@raspberrypi:~ http://<IP ADDRESS_OF_YOUR_DEVICE>/install/ bash: IP: No such file or directory pi@raspberrypi:~ http://<192.168.1.254>/install/
bash: 192.168.1.254: No such file or directory
pi@raspberrypi:~ ^C pi@raspberrypi:~


#8

Yeah you need to type the url on ANOTHER computer not the pi.
Also use a browser like what you are using for this forum.

At the top of the browser window that’s where the http://192.168.1.254 goes :wink:
Actually just try to click it.

EDIT: Also why did you install git?
And also if you have a smartphone use it to make a real photo of the screen after bootup.
Or do you ssh into the box?


#9

Seems you have attempted to install “Adsb-Receiver Project’s” Web Portal / Graphs


#10

If you have install ADSB-Receiver and you want to finish the installation…
If your Raspberry Pi’s IP address is 192.168.1.151

You should type:-

192.168.1.151/install at the WIndows based Browser or any other Linux Based Browser to gain access to the further installation process.

I saw from your screen’s photo shows the feeder-ID: d53c2c41-43c0-461c-abcc-305205cc56f1, it means you have your feeder-ID and you shall claim your feeder from the other PC browser with the link shown in your screen or https://flightaware.com/adsb/piaware/claim.

Good luck


#11

I am pretty confused about what exactly you are doing here and what image you started with. I don’t know what was on the sdcard in your prepackaged kit.

If you’re still having trouble I suggest you reimage the sdcard and start again so that things are in a known state. Follow the instructions of step 2 at https://flightaware.com/adsb/piaware/build. If you’re still having problems after that, please post a picture of the final screen after it’s finished booting (like the example I posted earlier)


#12

OK so when I type that address into another browser it brings me to my modem box settings and I can see that the raspberry is connected both via wired and wireless at this point. Is this what I was looking for? I wasn’t certain as to the reason why I was typing in the main IP address of my home network. But here is the picture attached.


#13

What I’m trying to do is get my PI aware box on line and feeding flight data for the first time. That’s as basic as it is it hasn’t been up and running yet I just got it a week ago.


#14

Why you have your Raspberry Pi’s Wifi & LAN connected to your router at the same time?

You only need to connect either LAN or Wifi at one time.


#15

so you still didn’t take the photo that was asked for, you do have a monitor connected to the RPi don’t you?

Also just type in the raspberry pis ip then and you should at least get the skyview map.
Or click this link: http://192.168.1.153 or wifi: http://192.168.1.157

Apart from that i have to agree that writing the sdcard with the new image and following the (very detailed) instructions would be best. Right now you don’t provide enough details. That makes it very hard to help.


#16

I just had an idea regarding the claiming process: Have you already entered a feeder-id somewhere, that is on the sd-card?


#17

I was just testing to make sure they both work but I disconnected the land just using wireless now.


#18


#19

Please type 192.168.1.157/install AT the Internet Explorer or Firefox or Google Chrome

NOT AT THE SSH TERMINAL.


#20

the problem with this photo is that it’s not after boot.

Do a reboot wait till it’s up and take a picture.