I have a Pi 3B+ and a ProStick + I can get the Pi running on my desk with the official Pi startup tools but anything I try to do with the ADSBexchange images seems to fail - My goal is really just to have the "custom" ADSBexchange software and dashboard running as simply as possible I thought that the "for beginners" section would lead me to a boot image, complete with all elements necessary and the custom interface/dashboard - and maybe it does? I just haven't been successful in using that data - When I install a "full" install, The full Pi desktop comes up and I am able to configure and connect to my wiFi and everything seems to be fine... What am I missing? clueless in california... Mark
Follow steps described here: https://www.adsbexchange.com/forum/threads/working-new-adsbexchange-base-image-v1-0.618988/ Very important, before you put card into Pi: Edit adsb-config.txt that is in the /boot partition of SD card. LATITUDE 3.366320 <- your lat LONGITUDE -11.694614 <- your lon ALTITUDE 400 <-your lat ADSBXCUSTOMPORT 30005 ADSBXNAME "feeder-name" <- enter uniqe username ENABLE_WIFI yes WIFI_SSID "SSID" <- your ssid WIFI_PASSWORD "password" <- your wifi password KEY_MGMT "WPA" ################# #DEFAULTS BELOW #DO NOT CHANGE #UNLESS NEEDED ################# MLATADSBXSERVER "feed.adsbexchange.com:31090" ADSBXCUSTOMURL "feed.adsbexchange.com" REMOTE yes PRIVACY yes <- change to no if you want te see pin on coverage map MLAT yes DUMP yes UPDATE no ENABLE_BT no SHELLBOX no UAT no UATPORT 30005 CELLULAR no WiFi configuration can fail, boot Pi with eth or keyboard and monitor and configure it with: Code: sudo raspi-config
MDA, I seem to be getting part way through the config process but there are error messages, tmp files not found, commands not found, no binary formatter found, falling back to text etc. When the adsbx-custom login: comes up - it doesn't accept either adsb/adsb or admin/admin and thats when you can get the text in before another command runs and overwrites it. It looks like my config file is set correctly and that my network is connecting but something else must be off... Is there a log file that captures the commands and messages? there are so many screens worth that I am not sure exactly what has failed and what has worked. Thanks Mark
MDA - Thanks! I think I am slowly getting what is going on and I AM able to connect to the dashboard and map - so my Pi seems to actually be functioning - I'm not quite sure hot to check if it is actually transmitting data to your servers, but it seems to at least be running locally - which I might need to call good enough for tonight...
Nice to hear, thanks for feeding. Go to https://www.adsbexchange.com/sync-1/ and check if your feeder name is present. If yes then everything works. Marcin
Marcin, Having worked on several "Enterprise Level" audio and video systems using network transport - your sync page is both fascinating and impressive - I understand that MLAT requires precision timing and after having routed thousands of high resolution audio streams, I know how much effort has to be applied to maintain a timed system - and the amount of mayhem caused by even a small number of improperly timed signals. It really is an impressive thing and fun to now be a part of providing to. My station will probably be somewhat intermittent initially as I refine a few things and attempt to make it completely independent and remote - solar with "Supercap" storage rather than batteries (nearly unlimited cycle life) and a shorter, higher quality antenna line. Hopefully the site will prove useful to the overall coverage! Thanks Mark
New "problem" that I know is just rocky ignorance... How can I stop the software running on the Pi so that I can run raspi-config or other commands w/o the running scripts typing over me? I haven't been able to get my wireless working yet and think it may be the country code? I don't care if its 2.4 or 5.8 (2.4 would probably be better for me) but I do need it to go wireless... Thanks Mark
You can run raspi-config regardless of running applications. Mlat-client and socat script have restart loop inside, you can kill them with SIGTERM using htop. Marcin
