Kindly pardon the NOOB question. I am setting up a new ADSBX/FA feeder. I see two config files: piaware-config in the root and the exact same file name in the adsb-exchange directory. Which of these files do I edit? (This is a new feeder, not yet claimed on FA.) I'm not sure why I'm seeing two config files here. Wondering if I made a mistake somewhere ... ;<) TU.
No thoughts on this, anyone? Edit either file and it makes no difference? (Hard to believe.) I'd like to get this feeder up before I leave this location later today -- far from my home. I can't recall what I did with the other feeders and there is no way to get into them from here to look.
Um ... the one in the adsb-exchange directory is probably a back up file. What image you are using? There 5 ways and different feeder images. The one you should edit is always the one in /boot
TU Mr James. Very helpful. I am using the file downloaded from this web site. Now trying to figure out if it is compatible with the Pi 3B+. All I get is a flashing red LED. I'll figure it out. The first three feeders went smoothly -- this one is goofy.
The FlightAware image is not Pi 3B+ compatible. The custom ADSBx v1.28 is. If you want to feed FlightAware, use thier most recent image and then install ADSBx using the script method. Code: sudo apt-get install git git clone https://github.com/adsbxchange/adsb-exchange.git cd adsb-exchange chmod +x setup.sh sudo ./setup.sh
TU James. It went "almost according to plan." When I installed ADSBX and ran the setup.sh I bypassed the lat/lon set-up as I did not know what those parameters were atthat time. My intention was to come back, run the setup again and enter them. Now I find the SSH credentials of pi/flightaware don't work. Google is not finding any references to other user/PW. So, two questions: 1. Will ADSBX read the lat/long entered into FA? Or must I run the ADSB setup again? 2. Is there a different lg-in that should be used? You've been very helpful. Very much appreciated. (I'm in an area of lots of "interesting" aircraft and there are very few ADSBX feeders. Getting this going is sorta light doing power-on stalls in a twin engine aircraft with one engine OTS. But I'll get it ... ) Rick
Those scripts need the lat/lon inputted for the MLAT client. You can manually edit the scripts in /home/pi/adsb-exchange adsbexchange_mlat_main.sh I think ... Or you can just rerun the setup, pretty sure that works too.
I'll give that a try in the morning. And, any idea why the default log-in of pi/flightaware does not work? The ADSBX script does not change this, does it?
Editing the script did not work for me but rerunning the script was painless. That worked. Thanks! One last question (for now ): The script requires entry of the elevation. The units are undefined in the setup screen and don't specify precisely what you're looking for. I took that to mean "meters above MSL to the rad center of the antenna." Yes/no? Could be other things e.g., feet above ground, etc.
Excellent! Just make best guess for antenna altitude, RF travels at the speed of light (300,000,000 meters/second). A few feet or a few miles doesn't make a difference. More important is that clock is kept in sync for MLAT as a very fraction of a second could be other side of the world.
Oh, I can actually measure the height. Just wondering if ADSBX MLAT wants the figure in meters or feet and AMSL or AGL. Curious about the "time," however. I note that FA periodically sends a warning on a couple of my receivers and drops them from MLAT calcs. THey always "recover" within a few minutes but I often wonder what the issue was to start with. From looking at my routers' records, looks like NTP is in use. If there's anything I can do better than that I'm all ears!
Doesn't matter. I think you can flag it with m or f ... but really ... it's not super important .. feet ...meters .. cubits .. whatever Unknown what FA is doing on their side, they don't share that information.
OK on the "measurements." Yea, I know there are "issues" with FA. But the fact that you [properly] emphasized the need for accurate time and they've flagged my data quite a number of times saying my clock was inaccurate makes me wonder what else I can do to ensure the data that emanates from my feeders is useful and accurate. Would have thought that a sync via NTP would be sufficient. Maybe not. Regardless, your help and advice is most appreciated. So, TU!
From google. sudo timedatectl set-ntp True Check result with timedatectl status In case of warning, you may have to run sudo timedatectl set-local-rtc tru https://raspberrypi.stackexchange.com/questions/47542/raspberry-pi-wont-update-time
