[WORKING] New ADSBExchange base image v1.0

Thanks, MDA.
I tried this site and getting a 404 Not Found.

 

that skybup is wild

Link is working again, Wasabi had infrastructure outage.

 

Hello everyone
I see a note about a release v1.29vlan:

But I can't find download link anywhere
In case it's still not released could anyone share an old image, please?

I've never seen such a thing (hiding old release even before a new one released) in any linux-related thread or community, unless there are bugs, drastically affecting core functionality or security >_<

 

Thanks for a quick reply, sorry to bother you with a question asked before

Setup is finally working, though I had a problem with connection to Wi-Fi.
It seems there is a "bug" with shell $-variable substitution in password from adsb-config.txt

E.g. password "prefix$notavar;suffix" produces just psk="prefix;suffix" in wpa_supplicant.conf
Changing " to ' fixes the trouble, though other troubles are coming with '.
The first workaround coming into mind is configuring password in a separate "/boot/wifi_password.txt" and just cat-ing it to the wpa_supplicant as is.

 

it's all bash feel free to edit scripts and fix it.

 

Fix is ready.
Tried to touch as little lines as possible.
Backward-compatible with old "adsb-config.txt"
Solution is giving an option to put password and/or SSID into separate files: /boot/wifi-ssid.txt and /boot/wifi-password.txt
If wifi-*.txt's are not empty, they are in priority.
Tested by running some manual variations on hardware raspberry.
Following files were patched:
├── boot
│   ├── adsb-config.txt - notes on how to setup complicated passwords
│   ├── wifi-password.txt - empty file for clarity
│   └── wifi-ssid.txt - empty file for clarity
└── home
    └── pi
        ├── adsb-config.txt.bak - copy of new default config
        ├── adsbexchange-getparams.sh - wifi credentials go into separate /tmp/adsbx-wifi-* instead of executable semiconfig /tmp/adsbx-params. Also fixed status output footer, bumped version 1.26->1.28
        ├── adsbexchange-wifi.sh - credentials carefully applied, via wpa_passphrase. setting to scan for hidden networks preserved
        ├── check-setup.sh - reading credentials from /tmp/adsbx-wifi-* instead of /tmp/adsbx-params
        └── resetdefaults.sh - added wipe of /boot/wifi-*.txt files

P.S. I've requested live data api key via contact form, though didn't receive any reply. How can I get one?

 

Interesting! I wasn't expecting someone to tackle this! I will take a look this weekend, if I can get the time.

 

thanks for this image, was trying to add stuff to noob image and getting nowhere fast. version 1.28 came up right away with the 1090 dongle... now trying with both the 1090 and 978 dongles installed. found note from Cam about "Eventually I discovered that in the adsbexchange-dump1090_maint.sh script that the --net-ri-port was set to 0 and I had to change it to 3001 in order to pipe in my UAT traffic to the local dump1090 instance." which i did except i think the port should be 30001. so put in 30001 and rebooted, but now how do i tell if it is working with uat?


hmmmm, i have a new pair of nesdr nano 3 dongles. i had been running just the 1090 one with a good outside antenna 180' above ground and getting lots of planes. i put in the 978 one and used just a Y cable to split the antenna to both of them and the signals went way down as did the max distance and signal strength... so i left both dongles in the pi and put the antenna only to the 1090 dongle and suddenly no signals, put the antenna on the 978 dongle and i get signals and planes. but they appear to be mode s reports. so shutdown and pulled the 978 dongle, put the antenna back on the 1090 one and restarted, now i'm back to the good signals and distance. could the 978 dongle have been trying to receive on 1090? going to leave it out for now until i figure out how to tell what each one is actually doing.

 

1.28 requires a little more messing to get 978 to work reliably.

1.29 has all the fixes needed.

You need will need to use

rtl_eeprom to set serial numbers to 1090 and 978 for the appropriate dongle.

 

ok, i'll hold out till 1.29. these dongles are nooelec nesdr nano 3, rtl_test reports the sn like "stx:1090:0" and "stx:978:0", would that have to be changed?

 

one more i forgot about till i went to move the pi to a more permanent location.... how do you set the adsb-config.txt for an unsecured wifi access point? also i get a notice that the country isn't set and to use raspi-config to set it, but it keeps complaining that it can't talk to wpa_supplicant. i found one suggestion to add a line to adsbexchange-wifi.sh, another to put an empty 'wifi' file in /boot, setting key_mgmt=NONE, but none of them seem to work. it is fine as long as i have ethernet plugged in but doesn't seem to want to talk to unsecured wifi.

 

Hey there,
I just installed the FlightAware-adsbexchange image to my pi and based it on my balcony. But I can’t find my feeder in the region. Is the name for adsbexchange the same as for FlightAware? There I can find my account and it’s feeding there.

 

Use the ADSBx image then add PiAware ...

Then check here from same Internet connection as the feeder.

https://www.adsbexchange.com/myip/

 

Didn't configure Wifi right did you?

 

didn't realize I could do it on my mbp before booting

now that it's up and running, when I have the monitor plugged in I get two types of messages, the first:

rc.local[541] No binary formatter available, falling back to text format
(this repeats about 15x)

the second is a read out of stats:

Date Receiver status: connected
Date Receiver server status: ready
Server 0.0 from server 0.0 TCP to server 0.0 UDP to server

Is the feeder not working correctly?

Btw, this is really excellent, thanks for doing this.

 

rc.local[541] No binary formatter available, falling back to text format

That's normal for this image.

Date Receiver status: connected
Date Receiver server status: ready
Server 0.0 from server 0.0 TCP to server 0.0 UDP to server

This likely MLAT.

Check here from same Internet connection as feeder.

https://www.adsbexchange.com/myip/

You should see 2 things. MLAT and beast.

You should have local map and dashboard on whatever IP it is on your LAN.

 

Strange, the myip page did display the MLAT and beast. (I'm at work right now and don't have access to my machine)

One other thing I noticed -- after it was up and running, my adsbx stats page showed "No Peers connected" (or No Peers found) for the majority of the night, only for 5 minutes did it switch to 91.5% health (with peers) and then revert back to no peers.

Also, I know from searching there is a lot of heat regarding this topic: how come the map for adsbx isn't the same map for GlobalRadarView on the main ADSBx site? I would love to have the same layers and design details with plane tracking.

Do I need to use dump1090? Could I write my own front-end using React or Vue and D3.js?

PS: Will feeding into adsbx slow down my internet connection? While feeding this am I had to VPN into work and things seemed slower. I unplugged my pi before leaving the house so will revisit all your feedback later tonight.

Thanks a million -- this is really incredible.