> You probably didn't restart fr24feed. Or it timed out > sudo systemctl restart fr24feed True. I didn't know about the restart command and I assumed that simply rebooting from the SSH prompt was sufficient to kick start everything. That didn't work. Eventually, I got frustrated and decided the Raspberry Pi 3 might need a shutdown followed by a power cycle. However, I was falling asleep at the keyboard, didn't bother checking if the uploads had returned, and just went to bed. In the morning (after oversleeping a few hours), I found that the feed had returned to normal and both Signal Level and Avg Signal Level were functioning normally. So, I won't need to update and reload dump1090-mutability. Here's what VRS and the signal level data look like at this time. http://www.learnbydestroying.com/jeffl/ADS-B/FR24/FR24-VRS-2020-10-08.jpg > sudo fr24feed-status pi@raspberrypi:~ $ sudo fr24feed-status [CODE] [ ok ] FR24 Feeder/Decoder Process: running. [ ok ] FR24 Stats Timestamp: 2020-10-08 16:35:38. [ ok ] FR24 Link: connected [UDP]. [ ok ] FR24 Radar: T-KWVI31. [ ok ] FR24 Tracked AC: 9. [ ok ] Receiver: connected (327423 MSGS/0 SYNC). [ ok ] FR24 MLAT: ok [UDP]. [ ok ] FR24 MLAT AC seen: 8. [/CODE] pi@raspberrypi:~ $ cat /var/log/dump1090-mutability.log [CODE] Statistics: Thu Oct 8 16:27:04 2020 BST - Thu Oct 8 17:27:04 2020 BST Local receiver: 8639610880 samples processed 0 samples dropped 0 Mode A/C messages received 15008433 Mode-S message preambles received 6997823 with bad message format or invalid CRC 7845975 with unrecognized ICAO address 152086 accepted with correct CRC 12549 accepted with 1-bit error repaired -39.8 dBFS noise power -18.3 dBFS mean signal power -1.5 dBFS peak signal power 164 messages with signal power above -3dBFS Messages from network clients: 0 Mode A/C messages received 0 Mode S messages received 0 with bad message format or invalid CRC 0 with unrecognized ICAO address 0 accepted with correct CRC 0 accepted with 1-bit error repaired 164635 total usable messages 2 surface position messages received 24209 airborne position messages received 22952 global CPR attempts with valid positions 0 global CPR attempts with bad data 0 global CPR attempts that failed the range check 0 global CPR attempts that failed the speed check 7 global CPR attempts with insufficient data 1131 local CPR attempts with valid positions 0 aircraft-relative positions 0 receiver-relative positions 128 local CPR attempts that did not produce useful positions 126 local CPR attempts that failed the range check 0 local CPR attempts that failed the speed check 0 CPR messages that look like transponder failures filtered 0 non-ES altitude messages from ES-equipped aircraft ignored 138 unique aircraft tracks 35 aircraft tracks where only one message was seen CPU load: 13.2% 269857 ms for demodulation 176472 ms for reading from USB 28734 ms for network input and background tasks [/CODE] pi@raspberrypi:~ $ cat /etc/fr24feed.ini [CODE] receiver="beast-tcp" fr24key="xxxxxxxxxxxxx" host="127.0.0.1:30005" path="/usr/lib/fr24/dump1090" bs="no" raw="no" logmode="0" logpath="/var/log/fr24feed" mlat="yes" mlat-without-gps="yes" [/CODE] Notice that I turned off logging. > Nothing but vrs in windows. You wont see any feeder going out. It's on the pi Oops (again). That explains why I didn't see any traffic on Windoze. Sorry (again). One more favor if possible. I found these dump1090-mutability diagnostic and control incantations at http://fuzzthepiguy.tech/dump1090-commands/ Is there something similar available for FR24? Extra credit for the names and locations of the various configuration files. [CODE] sudo service dump1090-mutability restart Restart Dump1090-Mutability sudo service dump1090-mutability start Start Dump1090-Mutability sudo service dump1090-mutability stop Stop Dump1090-Mutability cat /var/log/dump1090-mutability.log (Check Dongle) sudo nano /etc/default/dump1090-mutability Make Dump1090 changes sudo dpkg-reconfigure dump1090-mutability (The GUI way) [/CODE] Thanks for the assistance and details.