I’ve tried to read on how to maybe get Pi aware to run as a mobile install,but I’m still confused as to the proper steps needed.Can anybody give me a simple list of what I need to do? Do I need gpsd,a hotspot,etc?
I would like to be able to be at the Airport and see what flights are coming in and leaving while in the car.
Without GPS, it’s definitely not practical to update while the car is underway. I try to find a place to park where I can get a good visual on the air traffic and then update the PiAware coordinates for that particular observation spot.
What would you recommend for a Raspberry Pi / GPS interface? Preferably a GPS unit which is not a power hog.
We don’t officially support the GPS capability so I don’t have any particular recommendations for hardware as most setups don’t need it. I believe there are threads in the forums and some social media posts that describe setups that are configured this way.
As you are NOT feeding data, and are NOT participating in MLAT, it is not necessary, provided you are not far away (>300nm aerial distance) from the entered Latitude:Longitude.
The wrong location entry affects in two ways:
(1) On the map, the receiver location is shown wrong, and range rings are centered on wrong receiver location, but planes are still shoiwn on their correct location.
(2) Planes more than 300nm from receiver location are filtered out and not displayed on map and in flight table. If your actual location is more than 300nm from entered location, you wont see any planes on the map. The flight table will still show some planes, but these are “position-less”, i.e. no latitude and longitude was transmitted by these planes, and modeSDeco2 therefore does not know their location and does not filter these out.
Below are two screen shots which show this behaviour. My actual location is Toronto. I changed my Lat:Lon in .bat file to Lat:Lon of Ottwa, which is at 200nm aerial distance, and plane still showed at correct location, but rings got centered on Ottawa. I next changed Lat:Lon to that of Quebec City, which is at 400nm aerial distance. Rings got centered on Quebec City, and all the planes disappeared from map. The Flight table still showed planes, but only position-less i.e. those which did not transmit their Lat:Lon.
Entered Lat:Lon = 200nm (aerial distance) away from actual Lat:Lon
(Actual location Toronto, Entered location Ottawa)
Excellent.Thanks for the info.
Chrome wasn’t showing the Map,but I could see all the flights. Firefox was displaying the map fine though. After digging around I found out that Chrome has WebGL disabled by default. After I enabled it and restarted Chrome,the Map appeared.
(2) Plugged-in a USB flash memory stick (8Gb or more) in laptop and formated it.
(3) Wrote the downloaded .iso image to USB flash memory stick using Win32 disk imager (etcher can also be used).
(4) Shutdown laptop, and powered up again. At start up, entered option to select boot device (F12 one one laptop, Escape then F9 on other laptop, or somethibg similar, depending model of laptop), and selected USB flash memory as the boot device and booted from it into a Raspbian Pixel style desktop.
(5) Wifi was not working / not configurable. Connected a wired Internet. The driver for Wlan card of laptop was not included in .iso image. Gave following commands and the required driver got installed during upgrade:
sudo apt-get update sudo apt-get upgrade
Later Edit: due to some files getting corrupt, I formatted my USB Flash and wrote the Pixel x86 .iso image again. At first boot, I discovered in previous install, I had not correctly configured WiFi, and thinking that it is Wlan driver problem, did “sudo apt-get upgrade” which was not necessary and took a long time. The driver is available in Pixel x86 for my laptop’s wifi card (broadcom), and in the second fresh install, I could connect to WiFi without doing “sudo apt-get upgrade”.
The reason is these packages are built for ARM architecture (Raspberry Pi), whereas laptops have i386/amd64 architechture.
To install dump1090-fa (or dump1090-mutability) and Piaware data feeder, I build these from source, using J Prochazka’s scripts. Since these packages were built right on the laptop, these were built for the architecture of the laptop (i386/amd64).