I wanted to see if using raw data from port 30002 instead of beast data from port 30005 makes any difference in performance.
Configured FR24, RB24, Planefinder, and Piaware to use AVR data from port 30002 of dump1090. All feeders continued to feed normally after re-configuration, except piaware.
Sep 26 12:09:16 raspi-1 piaware[2592177]: mlat-client(2592194): Input connected to 127.0.0.1:30002
Sep 26 12:09:16 raspi-1 piaware[2592177]: mlat-client(2592194): Detected AVR format input
Sep 26 12:09:16 raspi-1 piaware[2592177]: mlat-client(2592194): Input format is AVR with no timestamps. This format does not contain enough information for multilateration. Please enable mlat timestamps on your receiver.
Sep 26 12:09:16 raspi-1 piaware[2592177]: mlat-client(2592194): Lost connection to 127.0.0.1:30002
Next did this:
sudo piaware-config allow-mlat no
sudo systemctl restart piaware
Now got following.
The “0 msgs recv'd from dump1090-fa” keeps on repeating.
Sep 26 12:19:33 raspi-1 piaware[2597892]: ADS-B data program 'dump1090-fa' is listening on port 30002, so far so good
Sep 26 12:19:33 raspi-1 piaware[2597892]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 127.0.0.1 --net-bo-port 30002 --stdout --lat 43.5xx --lon -79.6xx
Sep 26 12:19:33 raspi-1 piaware[2597892]: Started faup1090 (pid 2597908) to connect to dump1090-fa
Sep 26 12:19:33 raspi-1 piaware[2597892]: UAT support disabled by local configuration setting: uat-receiver-type
Sep 26 12:20:05 raspi-1 piaware[2597892]: 0 msgs recv'd from dump1090-fa; 0 msgs sent to FlightAware
Sep 26 12:25:05 raspi-1 piaware[2597892]: 0 msgs recv'd from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware
Sep 26 12:30:05 raspi-1 piaware[2597892]: 0 msgs recv'd from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware
Sep 26 12:35:05 raspi-1 piaware[2597892]: 0 msgs recv'd from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware
I never use the older port=30002 AVR text format unless I have some older software that does not support the beast binary on port=30005.
From memory, beast binary on 30005 always includes a raw data time stamp needed for mlat and other modes like PP beamfinder. The AVR on 30002 does NOT include a time stamp by default. The older versions of dump1090 used a “–mlat” command option to enable that time stamp for AVR, even though the documentation is a bit confusing with the explanation.
I just did a quick test using putty while watching AVR port=30002. I also enabled mode-a/c to make it easier to test. Initially, all the mode-a/c output lines were just the 4-digit mode-a squawk or mode-c altitude. By adding “–mlat” to dump1090-fa and restarting, the next putty connection to port=30002 now displays those mode-a/c outputs as longer. They now contain both the time stamp and the mode-a/c. The mode-s and ads-b messages also now contained the time stamps.
So, if you really want to test this, try adding “–mlat” and restarting.
I know of zero advantages to using AVR. I have used both, but always assumed that beast binary through the network was probably a bit more efficient to transfer.
If the old days with the earliest versions of dump109, many were using AVR with PP for mlat. All those used the “–mlat” command option for raw data time stamps. Almost everyone now has switched to beast binary on port=30005, which automatically includes that time stamp. The “–mlat” option is no longer required, but I still see it occasionally recommended in dump1090.bat files by folks that think it is required for mlat.
Current description of the “–mlat” command. This does not make it clear it actually impacts AVR output also. It does.
Just to make sure if the problem is with piaware/faup1090 or dump1090-fa, compilerd dump1090 (Antirez). This is very simple and doen NOT require installaing anything on Pi
git clone https://github.com/antirez/dump1090.git
cd dump1090
make
sudo systemctl stop dump1090
sudo systemctl stop lighttpd
./dump1090 --net --interactive
Checked FR24, RB24, Planefinder feeders. All working OK.
Checked piaware, no luck.
Sep 26 17:25:53 raspi-1 piaware[122984]: ADS-B data program '.' is listening on port 30002, so far so good
Sep 26 17:25:53 raspi-1 piaware[122984]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 127.0.0.1 --net-bo-port 30002 --stdout --lat 43.5xx --lon -79.6xx
Sep 26 17:25:53 raspi-1 piaware[122984]: Started faup1090 (pid 123655) to connect to .
Sep 26 17:30:24 raspi-1 piaware[122984]: 0 msgs recv'd from . (0 in last 5m); 0 msgs sent to FlightAware
Sep 26 17:35:24 raspi-1 piaware[122984]: 0 msgs recv'd from . (0 in last 5m); 0 msgs sent to FlightAware
