First of all Thanks for simplifying the process. I’ve been contributing for some years off and on and I still have lots to learn regarding “tweaking”. I have one question regarding this “Easy Button” install package.
The scenario: Many times recently, I am building my µSD with the piaware package in the office using the wifi in the office, but then when I go home I want to edit the wifi settings for my home wifi. With this “Easy Install” piaware package all I know to do is rebuild from scratch the µSD again using the home wifi info.
I looked for a “piaware-config.txt” file or other intuitive file to modify and didn’t find one. Can you tell me how to modify the wifi settings on a piaware install, so that I can update wifi settings when they change?
If you are using the adsb.im feeder image, if it can’t find a network, it will create a Wi-Fi hotspot that you connect to and then you enter the ssid and password over the web…
Thank you. I see that bullet point now on the adsm.im page. Since I was initially able to configure wifi, I discounted this bullet point all together, but then when I went to the hotspot page (Setting up WiFi for an ADSB.im Feeder) it was very clear.
While so far i’ve not seen any instances of the autogain presenting an issue i wanted to cast a wide net and ask if anyone is having issues with the changed autogain.
The charts show results with and without the LNA. Most of my experience has been with Airspy SDRs, so I’m not sure if the level of tracks with a single message on the Nooelec is an issue?
The sections without any single message tracks are when I swapped to an Airspy R2. The tests with the R2 (again with and without the LNA) have made me suspicious that there may be problem with the LNA, so I may be wasting your time.
cause of the single message tracks?
that’s normal and usually those are not passed to other programs so airspy_adsb gets them as well just doesn’t tell readsb about it.
I’ve had it running for about 10 minutes and only feeding FlightAware ATM. I have it connected to my network by WiFi. I did not set WiFi up using HotSpot method. I edited the file on the boot partition of the SDcard similar to how it’s done with PiAware images.
Feeding FA is working, but I see my local IP address shown in FA’s “My ADS-B” page is wrong. It shows: Site Local IP: 172.18.0.5, but my real local IP is 192.168.#.#
Also I’m not seeing the usual Green status boxes.
Wondering how to go about fixing these two issues.
That local IP address is specific to the way we implement feeding multiple aggregators. It’s the internal IP address of the container that runs the Piaware software.
This isn’t something we can easily fix.
Not getting the green market for successful feeding might just take a little while, not should eventually happen.
Make sure that you configure the exact same lat/lon in both adsb.im and for your feeder if the FlightAware website
The link to the FA status page doesn’t got to the correct page if you have multiple stations set up with FA.
So be sure you’re looking at the correct station.
You can also check the log for the piaware container.
Yes, I have two sites. Florence, South Carolina and at my home in Alachua, Florida.
The Florence site is untouched running the FA Piware build. I get the green boxes.
It’s the Alachua site running ADS-B Feeder having the troubles for now; no green boxes after about 8 of operation.
I see if I can make sense of the log in piaware container.
Thanks!
Following is my personal preference. I know many users have different preferences. Everyone to his own.
To keep my install simple. I dont unnecessarrily add an extra layer of docker, when I can directly install and run all types of decoder and feeder software. Piaware SDcard image is a very easy solution even for a novice and beginner.
The green status boxes as shown in the image from my Florence, SC site.
You’re right, everything’s working. Status in the ADSB-Feeded app shows good.
Not a deal-breaker at all; just pointing it out in case I did or configured something wrong.
Thanks!
(1) Using piaware_builder source code on Debian/RaspberryPi OS/Ubuntu/DietPi etc to build piaware .deb package, successfully provides the 3 Green Boxes on status page
(2) The piaware_builder source code does not built on non-Debian OS as it is designed for deb packages. However piaware can be build using piaware sourcecode on Fedora, ArchLinux etc, but results in missing green boxes.
Anyone had problems with wireless network disconnecting? I had this happen to this new build last night.
The same sort of thing has happened to another Bookworm 64 Pi 4 of mine.
This may not be the best place to ask, but since this sits on top of Bookworm I thought I’d ask.
BTW, I have a Raspi-NOAA Pi 4 running Bookworm that’s been doing the same thing, wired connection as well. There have been some changes to my home’s networking, but older the older version of FA never had the problem, and that goes for the Wx satellite build as well.
Thanks again!
You probably got the image based on raspbian, so it’s just networkmanager like on stock raspbian.
Think the piaware image is a raspbian version behind? Not sure.
If you’re having to cycle power to get it back on the network, enable persistent logging on the management page.
Once the issue happens again, “management → share diagnostics” and send me a link via direct message. I can check if i can see anything in the logs.
If it comes back onto the wifi on its own you can just send me the logs without extra steps.
Thanks abcd567 for that answer!
My Google research led me to trying this nmtui command on my Raspi-NOAA system which is supposed to turn WLAN power saving off:
sudo nmcli c modify MatrixExt-H 802-11-wireless.powersave 2
Too early to tell if it’s working. However, if I’m going in the right direction, how is the best way to get this set up on the ADSB-feeder system?
Cheers!
