||Installed FlightRadar24 feeder on RasPi-7, but it didn't seem to be connecting to the dump1090 server on port 30005. Seems this needs to be configured as receiver="beast-tcp" rather than "avr-tcp" in the /etc/fr24feed.ini file. It then worked as expected.
||Updated PiAware to 2.1-2
||Updated PlaneFinder client to 3.0.2080
||Added PlaneFinder client 3.0.450 to RasPi-7. Noted about 7% CPU increase and about 30 MB memory increase.
||Changed to RasPi-7 and PiAware 1.20
||Added filter & pre-amp, better results
||Updated PiAware to 1.18
||Updated PiAware to 1.15
||Updated PiAware to 1.13
||Discovered that RasPi-3 hadn't been uploading to Plane Plotter since Sep-06 at 19:35 UTC. Restarted the 1090 processes.
||Updated PiAware to 1.11
||Updated PiAware to 1.9
||Updated PiAware to 1.8
||Installed PiAware 1.5 on RasPi-3
||Updated dump1090 to V1.09.0608.14.
||Updated dump1090 to V1.08.2705.14 which has more network buffering. Noticed a welcome CPU drop from ~35% to ~32%, which gave a slight CPU temperature drop too.
||Connected back to the EDI-facing Yagi antenna.
||Connected to main antenna instead of the EDI-facing yagi, and changed PC Alta (share tD) from The Mode-S Beast to the RPi for a test for John Locker.
||Add --modeac to the parameters to add mode-A/C decoding. This increased the CPU load from averaging 35% to 45%. Dropped in early April.
||Updated to version 1.08.1003.14 which has a heartbeat to keep the connection with Plane Plotter alive.
||Client PC Ystad is being fed from a microADSB receiver for a temporary test, so it will have no Wi-Fi I/O from the Raspberry Pi server. This also means that the Raspberry Pi is only feeding one PC with data rather than two, so its I/O rate would be expected to be halved.
Unexpectedly, this has rsulted in PC Stamsund's Plane Plotter restarting the TCP connection often during the night when there has been little traffic.
||Updated dump1090 (and ppup1090) to version: 1.08.2302.14. Fixes: (1) missing blocks cause timestamp slips, and (2) incorrect beast binary input/output handling of 0x1a escape characters, but neither should affect my own system.
||Edited /etc/init.d/dump1090.sh to include the ppup1090 program following suggestions from Steve Tickle. This allows the ppup1090 program to start automatically with the rest of the RPi. Tested by a warm reboot. Details are here.
||RasPi-3 seemed to stop working at about the same time as I was setting up a new iPad with iOS-7. Co-incidence? Restarted OK, and did a manual start of ppup1090
||Restarted PPupload function, as it had not been restarted at the Oct-20 reboot. dump1090 is at version 1.07.0710.13
||Updated dump1090 to 1.07.06.10.13 to add the PPupload functionality.
||RasPi-3 went off the air, not pingable. Power-off restart at 20:10, and it looks OK.
||Updated dump1090 program to version 1.07.1908.13. Rebooted RasPi-3 to ensure it started OK, and to get a standardised starting condition.
||Noted a zero message rate on PC Ystad from RasPi-3 dump1090 program.
Tried pinging RasPi-3 and that was OK, tried stopping and restrting
Plane Plotter but that didn't help. Tried closing and re-opening
Plane Plotter but that didn't work. On RasPi-3, the dump1090 process
was running (1 day 8 hours out of 8 days 36 hours up-time), but did a
restart (sudo /etc/init.d/dump1090.sh start) and the TCP started
flowing once again.
||PC taking data from RasPi-3 showed no planes and zero message rate. RasPi-3 responding normally, and dump1090 process still running. Next time I looked, Plane Plotter had started seeing data again, so its automatic restart of the TCP/IP connection seems to have resolved the issue.
||dump1090 appeared to have stopped sending data, so restarted it.
||Updated dump1090 to 1.06.1405.13.
||Added PC Ystad back in as receiver PC, RasPi now feeding two PCs.
||Changed receiver PC from Ystad to Stamsund.
||Moved the Raspberry Pi to the shack, connected to a yagi antenna pointing at the airport.
||Moved the Raspberry Pi back to the spare room, may have been causing interference to 137 MHz APT reception. Mag mount antenna wasn't well located.
||Updated dump1090 to 1.01.1924.13. Got start/stop script working.
||Playing with script to start and stop dump1090, buffer size now 150. Later, buffer size: 500, number: 5.
||Updated dump1090 to 1.00.1404.13 with buffer size 100. May reduce CPU overhead.
||Moved the Raspberry Pi into the loft, slightly better antenna.