Problem getting FlightAware Raspberry Pi software to boot

FlightAware ADS-B Flight Tracking
21

When I enter startx, I receive the following message: -bash startx: command not found.

I see you attempted to use the scripts or image from raspberrypi.org/downloads/raspbian/. Once you have written the image to an SD card and have booted it up simply run the manual installation commands under “Obtaining And Using This Software” in my original post. This will clone a copy from the repository containing the scripts for you and execute setup.


sudo apt-get update
sudo apt-get install git
git clone https://github.com/jprochazka/adsb-receiver.git
cd ~/adsb-receiver
chmod +x install.sh
./install.sh

After running ./install.sh you will be asked if you want to update your OS as well as what software you wish to install. In order to setup your receiver to be as close as possible to the official PiAware image install dump1090-mutability, skip dump978, and select PiAware from the feeder list. You can skip the web portal if you like but it does contain some cool features such as performance graphs.

If you do not need a GUI I suggest using the image.

If you use the image after booting it up run the command “cd ~/adsb-receiver/; ./install.sh”. This will allow you to configure dump1090-mutability to your location. After doing so run ./install.sh once more. Skip reinstalling dump1090-mutability, skip dump978, select PiAware from the feeder list. Again you can skip the web portal if you wish.

Either way make sure to expand the file system using the raspi-config utility right after booting up your RPi before doing anything else.

Installation and upgrade instructions:
github.com/jprochazka/adsb-rece … /README.md

More information on the image I have available can be found here:
github.com/jprochazka/adsb-rece … iver-Image

If you have any questions feel free to ask.
Good luck!

22

Sounds like jerry needs the GUI one time only to set up wifi.
I also sometimes have isses running startx fronm ssh in noobs.
Using noobs or rasperian, I have found that initially its best to hook up to a hd tv to get the wifi and system essentials sorted in the GUI along with system password, apt-get update/upgrade etc.
Once all this is done and the pi is sitting on the network and its happy, time to reboot and unhook the tv, keyboard and mouse.
From the next boot its always pi in unattended headless operation, if i need to change anything, I connect via ssh with Putty from laptop/PC.

If you are using just the project image,

Firstly the easiest way to set essentials is


cd ..



sudo raspi-config

Then there will be some work for you working as root to set up the wifi using nano editor.
(I suggest setting the address of the pi to a static one.)


sudo nano /etc/network/interfaces

and


sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

Good Luck Jerry.

23

You can also do it without the GUI. I setup wifi through the command line via /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf.

24

Right on jrorci.
Setting up wireless from the “command line” really isn’t that hard.

Make sure wpa_supplicant is installed.


sudo apt-get update
sudo apt-get install wpasupplicant

Edit /etc/wpa_supplicant/wpa_supplicant.conf.


sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

Generally it will look like the following unless your wireless access point is using a non conventional configuration.
Be sure to replace ssid with the ssid of your access point and psk with your access points password.


ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
        ssid="YOUR_SSID"
        psk="YOUR_PASSWORD"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        auth_alg=OPEN
}

Then open the file /etc/network/interfaces.


sudo nano /etc/network/interfaces

Add the following if a wlan0 section does not exist.


allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Forgot to add after your done run the following command.


sudo ifup wlan0

Being scared of the command line can make things more complicated then they should be at times. :slight_smile:
Then again I live in the command line on Linux.

25

Is auto wlan0 required so wifi comes online on boot?

26

No it shouldn’t be.
allow-hotplug I think handles that.

One thing I did forget was to run the following command after your done.


sudo ifup wlan0
27

The last thing that may come in handy – since you’re going to be putting your Pi in the attic – is a static ip address. That way you can access the Pi remotely via SSH, and it will always have the same IP. Your network settings may vary, but on mine I added the following lines to the /etc/network/interfaces file:



iface default inet static
address 192.168.1.150
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1

The “address” line is the IP you want to assign to the Pi. The others are dependent on your individual network settings.

28

Great suggestion with you again jrorci.
Another thought set your router to assign the MAC address of your RPi a specific address whenever it connects if the option is available that way you can keep using DHCP on your RPi and not have to deal with extra configurations if God forbid you have to rebang your device. Either way the same result just throwing it out there. :wink:

Edit:
Just realized some might not understand “rebang”. It comes from my BBS days running TradeWars. Bascally it refers to when you would recreate a universe basically resetting the server and starting from scratch. A saying that has stuck around in the local inner circle. Big Bang → Re Bang :smiley:

29

I have a setting on my router to “keep address for XX days” where the maximum is 30.
I use this feature to retain the static address i selected and wrote in supplicant.conf.

One of the main problems for me was the pi would " fall asleep" in low traffic conditions/early hours.
It is a struggle with low traffic activity and power saving functions of WiFi adapters.

On my main feeding station pi running rasperian from noobs ,As a workaround i use a script called wifi check and set up a job in cron to run it every minute/every hr/every day.

github.com/dweeber/WiFi_Check/b … WiFi_Check

Since installing jprochazkas project adsb-receiver on which there is a long thread about, I have not had to use this workaround as cron keeps the pi busy with graph generation etc so my pi is very happy chugging away with no such intervention.
Since installing adsb-receiver on a test spare pi b+, I’m surprised as to how little intervention is required and the very low disk space usage.
If you want a quick setup, good user interface with no hassle adsb-receiver is for you.

30

I got same issue as yours, I write a TF card with Piaware image, when it power on, rainbow screen. Then I format the TF card and rewrite Noobs image, works fine, I think Piaware image should update.

31

Thanks to all for your suggestions. I’ve had to put this project down for a couple of days, and hope to be able to hit it on Saturday.

I’ll check back in with good or bad news.

32

You can add: wireless-power off
Into /etc/network/interfaces.d to prevent wifi power down.

33

OT: :wink:

BBS. The good old days… Fido Net… running a BBS on an Amiga 4000 which is still here (at the attic, not running… no place free, because of the raspberries with antennas :slight_smile: ) with DLG Software and a V.32bis Modem… just about 6.000 US$ at the very early 90s… for the Amiga, modem and software… also got a “cheap” 1(!)GB-HDD (SCSI of course) when travelling to Atlanta… just for… 1.000 US$ (1 US$ per MB) … And of course I don’t want to remember the phonebill… .:slight_smile:

34

Progress, I think.

I ran Noobs, and then downloaded the software from Flightaware.

Flightaware’s found my receiver:

"PiAware - Claim and Link a Brand New PiAware Ground Station

Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware connection yet from your IP (75.71.43.253 or 2601:283:4401:65ab:cdfa:3c32:84a2:9930). Either your device has not yet connected (it takes a few minutes to start) or you are on a different IP address.

FlightAware searches for PiAware connections on the same global IP (75.71.43.253 or 2601:283:4401:65ab:cdfa:3c32:84a2:9930) 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.

Check Again for my PiAware Setup Manually with HDMI display + keyboard (advanced)

Linked PiAware Receivers (JerrytheK)

Great news! Your account is associated with the following PiAware receivers and you can view your statistics here:

b8:27:eb:93:8f:bd: PiAware (Debian Package Add-on) 2.1 added Monday, March 21, 2016 (75.71.43.253 / 10.0.1.65)"

Again, pardon my extreme lack of knowledge, but I think I need to set a new static address.

Could someone please walk me through that?

My router address is 75.71.40.1

The wireless/wired router’s (Airport Extreme) address is 75.71.43.253

The Raspberry Pi IS showing up as a client on the wireless network.

I have the setup and antenna sitting outside, so it does have clear line of sight to the sky.

As always, thanks!

35

The text you have supplied show it looks good.

Give it an hour or so for the stats page to populate.

36

Jon, will do.

I may give it all night, if it’s not up in an hour or so.

Thanks for the help!

And using various network apps on the Mac, the R Pi is showing up on the internal networks.

37

Kudos on getting set up, Jerry! If you want to see whether you’re tracking anything in realtime, try the following. Open a web browser that’s on the same network as the pi – then type in the local IP address of the pi – followed by port 8080. For example, mine would be:

192.168.1.150:8080

It should give you a map with an overlay of the planes you’re tracking…

38

Thanks.

Just tried that and get the following error message:

This site can’t be reached

10.0.1.65 refused to connect.
ERR_CONNECTION_REFUSED

I just pulled the pi’s address from a network utility.

Any thoughts?

39

Odd. I thought the dump1090 install came with port 8080 already setup. Try…

raspberrypi:8080

Unless you named the raspberry pi something else during setup… If you did, use that name instead.

40

raspberrypi’s the name that shows up in the network.

Tried raspberrypi:8080

Doesn’t want to connect to that either.

In the Mac’s Network Utility I’m getting:

Port Scan has started…

Port Scanning host: 10.0.1.65

 Open TCP Port: 	22     		ssh

If I use raspberrypi as the scan target I get

Port Scan has started…

Cannot find host: raspberrypi
Port Scan has completed…

Thanks!