![]() 20:01:24 no ADS-B data program is serving on port 30005, next check in 60s 20:00:23 no ADS-B data program is serving on port 30005, next check in 60s 20:00:04 server is sending alive messages we will expect them 19:59:23 no ADS-B data program is serving on port 30005, next check in 60s 19:59:04 logged in to FlightAware as user lovelacm 19:59:04 manualUpdate in /etc/piaware is enabled, allowing update 19:59:04 autoUpdate in /etc/piaware is enabled, allowing update 19:59:04 encrypted session established with FlightAware 19:59:04 FlightAware server SSL certificate validated 19:58:23 no ADS-B data program is serving on port 30005, next check in 60s ![]() 19:58:08 0 msgs recv'd from (not currently connected to an adsb source) 0 msgs sent to FlightAware 19:57:23 no ADS-B producer (dump1090, modesmixer, etc) appears to be running or is not listening for connections on port 30005, next check in 5m ![]() 19:57:23 no ADS-B producer program seen for 0 seconds (or since piaware started), will attempt to start it next check after 360 seconds. 19:57:23 no ADS-B data program is serving on port 30005, next check in 60s 19:57:23 got 'couldn't open socket: no such device or address (Temporary failure in name resolution)' to adept server at /1200, w 19:57:23 connecting to FlightAware /1200 19:57:23 your system info is: Linux piaware 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53: armv7l GNU/Linux 19:57:23 piaware version 1.20 is running, process ID 2091 My output file looks like this, and shows the fact that I had to manually ask fadump1090 for a restart just a couple of minutes ago: Rebooted and gave it some time… ran a piaware-status with these results:ĭump1090 is listening for connections on port 30005.ĭump1090 is listening for connections on port 10001. I’ve moved my piAware around in a different window to see if I can get more clear sky… Looking for some troubleshooting help… kicks in the right direction… etc. I currently live in an apartment building with relatively little line of sight to a large piece of sky, but I should be getting something from my receiver (NooElec R820T), right? 15:18:51 0 msgs recv'd from dump1090 (0 in last 5m) 0 msgs sent to FlightAware 15:18:21 dump1090 is listening for connections on FA-style port 10001 15:18:21 seconds since last message or startup (2700) less than threshold for action (3600), waiting. My output file is another matter… as once the programs get up and running, I constantly get this time-based update as the system has no data to work with, so it resets itself: I did a whole bunch of reading about piaware statuses and such… and mine looks pretty well inline with all of yours… I put my kit together, setup the WiFi, plugged in the SDR/ADS-B dongle w/ antenna… and waited… and checked the logs… and waited… and checked the logs… Greetings from a noob to the Raspberry Pi and the piAware scene.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |