OK, it was my fault to begin with by not backing up my SD before it crashed a few days ago (Ver 6.0 recently updated) I have had to rebuild from the beginning with a download of Ver 6.1. I captured the feeder_id from my status page and added it to the piaware-config.txt file. The system started ok and SkyAware is working. SSH works fine so the IP address is exactly the same as before. Below is the output from -status. It indicates that I’m not connected to Flightaware and I don’t have a feeder ID yet.
It’s been well over 30 min with no indication that any connection has been made yet.
I may have overlooked something so I would really appreciate any suggestions/recommendations.
Thanks for any assistance,
pi@piaware:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 521.
PiAware ADS-B client (faup1090) is running with pid 599.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 518.
dump1090-fa (pid 518) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.
dump1090 is producing data on localhost:30005.
You don’t have a feeder ID yet.