Piaware not receiving data from FR24 new LCD unit on BS Port 30003

behrozaltaf · July 30, 2021, 1:29pm

Hello fellow trackers,

I have a new FR24 LCD unit which transmits basestation format on port 30003. I have tried all possible configs for ‘receiver-type’ in piaware-config.txt to somehow get data but the Piaware page insists it is not connected with the receiver.

The Piaware does get connected with the FR24 unit with ‘receiver-type relay’ on port 30334 but that port does not transmit position-less (Mode-S) data. I therefore cannot participate in MLAT data sharing.

Please guide as to which receiver-type to be selected in piaware-config.txt to feed Piaware correctly along with Mode-S data.

Regards,
Behroz Baloch
Gwadar, Balochistan.

obj · July 30, 2021, 4:14pm

PiAware needs raw Beast-format messages. 30003 is usually associated with processed SBS-style output; piaware cannot use that data.

If the FR24 hardware doesn’t forward all raw messages externally I’m not sure it’s going to be very useful.

abcd567 · July 30, 2021, 7:18pm

Adding following line in file /etc/fr24feed.ini will open port 30005 of fr24feed-controlled dump1090-mutabilty EB_VER:

procargs="--net"

Restart fr24feed after adding and saving above line

wiedehopf · July 30, 2021, 8:54pm

There is zero user configuration on those devices i believe.

abcd567 · July 30, 2021, 9:47pm

You mean he is using the FR24 supplied receiver. I misunderstood that he is using FR24 feeder on RPi with 3.5" LCD display added.

abcd567 · July 31, 2021, 7:00am

@behrozaltaf

Your FA Stats page shows that you are using Piaware SD card image 5.0. You can therefore install ModeSMixer2 on the Raspberry Pi and configure it as given below. Please note that the dump1090-fa is also running, which will receive MLAT feedback results on port 30104 and show it on Skyaware map. Further, the port 30005 is in use by dump1090-fa, so modesmixer2 should use another port say 31005

Configure ModeSMixer2 as follows:

--inConnectId 192.168.0.22:30003:FR24 --outServer beast:31005 --web 8787
**Note: in above configuration, replace 192.168.0.22 by the local IP of FR24 Receiver**
Configure Piaware as follows to use data from ModeSMixer2

sudo piaware-config receiver-type other sudo piaware-config receiver-port 31005 sudo piaware-config receiver-host 127.0.0.1

$ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-07-31 03:05:25 EDT; 1min 31s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 30593 (piaware)
Tasks: 6 (limit: 2065)
Memory: 9.6M
CGroup: /system.slice/piaware.service
├─30593 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─30606 /usr/lib/piaware/helpers/fa-mlat-client --input-connect 127.0.0.1:31005 --input-type auto --results beast,connect,localhost:30104 --r
├─30609 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 127.0.0.1 --net-bo-port 31005 --stdout --lat 43.xxx --lon -79.xxx

Jul 31 03:05:29 orangepipc piaware[30593]: mlat-client(30606): Detected BEAST format input
Jul 31 03:05:29 orangepipc piaware[30593]: mlat-client(30606): Input format changed to BEAST, 12MHz clock
Jul 31 03:05:29 orangepipc piaware[30593]: mlat-client(30606): Beast-format results connection with ::1:30104: connection established
Jul 31 03:05:30 orangepipc piaware[30593]: piaware received a message from modesmixer2!
Jul 31 03:05:35 orangepipc piaware[30593]: piaware has successfully sent several msgs to FlightAware!
Jul 31 03:06:00 orangepipc piaware[30593]: 19 msgs recv’d from modesmixer2; 19 msgs sent to FlightAware

~~# Automated script to install ModeSMixer2~~

EDIT:

(1) Please see my next post.
(2) Please do NOT use above method. Although above method succeeds in converting Basestation to Beast and feeds Beast data to Flightaware, for some reason their MLAT Servers do NOT synchronize with other receivers, as the comment “Synchronized with xxx nearby receivers” is missing. Please see screenshot below.

wiedehopf · July 31, 2021, 10:36am

I’ll just leave it to @obj to object to advertising this.
There is a reason piaware doesn’t accept the basestation data format.
And it’s not that they didn’t want to write the code to ingest it, that part is easy.

abcd567 · July 31, 2021, 2:28pm

I have now tried another way, and it succeeds:
I dont have FR24 Supplied Receiver, but have fr24feed installed on another RPi at Local IP 10.0.0.23 with following settings

I changed RAW data from NO to YES as below, so the raw data (beast) is available from FR24FEED on RPi at 10.0.0.23:30334

Next reconfigured Piaware at another RPi at 10.0.0.21 as follows:

sudo piaware-config receiver-type other
sudo piaware-config receiver-port 30334
sudo piaware-config receiver-host 10.0.0.23
sudo systemctl restart piaware

Now the status shows “Multilateration (MLAT): Supported / Enabled (synchronized with 212 nearby receivers)”

pi@piaware:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-07-31 10:07:46 EDT; 18min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 18963 (piaware)
    Tasks: 6 (limit: 2062)
   CGroup: /system.slice/piaware.service
           ├─18963 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─19005 /usr/lib/piaware/helpers/fa-mlat-client --input-connect 10.0.0.23:30334 --input-type auto --results beast,connect,localhost:30104 --resu
           ├─19006 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 10.0.0.23 --net-bo-port 30334 --stdout --lat 43.xxx --lon -79.xxx
           └─19009 /usr/lib/piaware/helpers/faup978 --connect localhost:30978

Jul 31 10:18:22 piaware piaware[18963]: 2852 msgs recv'd from the ADS-B data program at 10.0.0.23/30334 (1307 in last 5m); 2852 msgs sent to FlightAware
Jul 31 10:18:22 piaware piaware[18963]: 1 msgs recv'd from dump978-fa (0 in last 5m); 1 msgs sent to FlightAware
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Receiver status: connected
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Server status:   synchronized with 211 nearby receivers
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Receiver:  253.9 msg/s received      117.7 msg/s processed (46%)
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Server:      0.1 kB/s from server    0.0kB/s TCP to server     0.9kB/s UDP to server
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Results:  20.9 positions/minute
Jul 31 10:22:52 piaware piaware[18963]: mlat-client(19005): Aircraft: 12 of 18 Mode S, 27 of 41 ADS-B used
Jul 31 10:23:22 piaware piaware[18963]: 4055 msgs recv'd from the ADS-B data program at 10.0.0.23/30334 (1203 in last 5m); 4055 msgs sent to FlightAware
Jul 31 10:23:22 piaware piaware[18963]: 1 msgs recv'd from dump978-fa (0 in last 5m); 1 msgs sent to FlightAware

abcd567 · July 31, 2021, 4:03pm

@behrozaltaf
@obj

I feel the reason @behrozaltaf is unable to get MLAT planes is NOT the poor quality of data from FR24 Receiver. This was demonstrated in my last post above.

In my opinion it is most likely due to non availability of enough nearby receivers to synchronize with. Please see map of Flightaware receivers in the location around @behrozaltaf’s 3 receivers.

obj · July 31, 2021, 7:43pm

As wiedehopf says, please don’t do this. We want to see the original raw messages, not whatever MM2 makes up based on the incomplete information available in the port 30003 feed.

(And it will absolutely not work with mlat because the made-up messages don’t have anything like good timing info)

obj · July 31, 2021, 7:45pm

I don’t know if it’s true of the latest hardware versions, but previous versions of FR24 hardware deliberately crippled the message output (by rounding timestamps) so that you can’t use it for mlat.

abcd567 · July 31, 2021, 8:00pm

Thanks for clarification. Actually I came to same conclusion and have already added following note to ModeSMixer2 post.

abcd567 · July 31, 2021, 8:53pm

This is too bad!

As I dont have FR24 supplied Receiver, I could not test it’s port 30334 output.

Instead I tested Raw data output from port 30334 of their feeder “fr24feed” intalled on RPi. The fr24feed is configured to get its input from dump1090-fa port 30002. Piaware was configured to use output from port 30334 of fr24feed, and works perfectly well, with MLAT Enabled and synchronized with over 100 nearby stations. However the results of RPI feeder may not be applicable to FR24 hardware.

behrozaltaf · August 2, 2021, 2:14pm

Thank you @abcd567 and @obj for all the help.
Well I tried all the configurations you people shared however Piaware was unable to process data on both port 30334 and 30003 from FR24 unit. I tried the same config on Planeplotter but was receiving MLAT data, however Planeplotter was not receiving mode A/C data. I also have an old FR24 Radarcape unit which used to provide full data on port 30334 but my Piaware is no more receiving MLAT and Mode A/C data possibly showing that FR24 had done something to restrict MLAT and Mode A/C on these port.

So after all it seems I cannot use FR24 units for positionless data.
@abcd567 @obj I would like to ask another way if you can help. I have a Planefinder Unit as well which transmits on port 30054 (not sure of the actual format but is known as Planefinder format). Is there any way I can feed Piaware on this port since Piaware also is not receiving data on ‘relay’ and ‘other’ receiver type from this unit.

Regards.

abcd567 · August 2, 2021, 6:17pm

@behrozaltaf
In view that both FR24 and Planefinder have done somthing with the output of their receivers to make them unsuitable to feed other sites, your best bet is to apply to Flightaware for their receiver.

The Flightaware feeder map shows that you are the lone Flightaware feeder from all the three sites (Gawadar, Karachi, & Quetta), you will most likely get Flightaware Receivers. May be Flightaware staff @obj and @eric1tran can help you in this regard.

In unlikely case of Flightaware declining your request, you may purchase a Dongle (Flightaware Pro Stick Plus) and an an antenna (Flightaware 1090 Mhz Antenna) from Amazon.com. You already have RPis running Piaware SD Card image at all 3 locations.

abcd567 · August 2, 2021, 6:27pm

I dont have Planefinder Receiver.
I feed their feeder “pfclient” installed on RPi.
The pfclient gets its data from dump1090-fa port 30005.
The “pfclient” outputs data on port 30054 in beast format.

I changed Piaware settings as below:

pi@piaware:~ $ sudo piaware-config receiver-type other
Set receiver-type to other in /boot/piaware-config.txt:89
pi@piaware:~ $ sudo piaware-config receiver-port 30054
Set receiver-port to 30054 in /boot/piaware-config.txt:90
pi@piaware:~ $ sudo piaware-config receiver-host 127.0.0.1
receiver-host is unchanged
pi@piaware:~ $  sudo systemctl restart piaware

With above change of feeding Piaware, it still feeds successfully Flightaware with MLAT synchronized with over 200 stations. However this most likely wont be the case when Piaware is fed from Planefinder’s hardware.

pi@piaware:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-08-02 14:00:12 EDT; 18min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 17917 (piaware)
    Tasks: 6 (limit: 2062)
   CGroup: /system.slice/piaware.service
           ├─17917 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─17944 /usr/lib/piaware/helpers/fa-mlat-client --input-connect 127.0.0.1:30054 --input-type auto --results beast,connect,localhost:3010
           ├─17947 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 127.0.0.1 --net-bo-port 30054 --stdout --lat 43.xxx --lon -79.xxx
           └─17950 /usr/lib/piaware/helpers/faup978 --connect localhost:30978

Aug 02 14:10:47 piaware piaware[17917]: 2751 msgs recv'd from pfclient (1218 in last 5m); 2751 msgs sent to FlightAware
Aug 02 14:10:47 piaware piaware[17917]: 3 msgs recv'd from dump978-fa (0 in last 5m); 3 msgs sent to FlightAware
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Receiver status: connected
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Server status:   synchronized with 212 nearby receivers
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Receiver:  374.4 msg/s received       85.3 msg/s processed (23%)
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Server:      0.1 kB/s from server    0.0kB/s TCP to server     0.8kB/s UDP to server
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Results:  23.5 positions/minute
Aug 02 14:15:17 piaware piaware[17917]: mlat-client(17944): Aircraft: 9 of 18 Mode S, 22 of 37 ADS-B used
Aug 02 14:15:47 piaware piaware[17917]: 4039 msgs recv'd from pfclient (1288 in last 5m); 4039 msgs sent to FlightAware
Aug 02 14:15:47 piaware piaware[17917]: 3 msgs recv'd from dump978-fa (0 in last 5m); 3 msgs sent to FlightAware

system · August 2, 2022, 6:27pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Piaware fails to get data from dump1090 port 30002 ADS-B Flight Tracking	3	126	September 26, 2024
FR24 up and running for 2 years with RPi, PiAware installation not working ADS-B Flight Tracking	11	4151	March 19, 2018
Is it easy to feed FR24 from a piaware 3.7.1 image? ADS-B Flight Tracking	24	2053	August 30, 2019
Piaware and FlightRadar24 together ADS-B Flight Tracking	26	34374	March 3, 2017
PiAware Feed ADS-B Flight Tracking	15	3235	January 25, 2018

Piaware not receiving data from FR24 new LCD unit on BS Port 30003

Configure ModeSMixer2 as follows:

Configure Piaware as follows to use data from ModeSMixer2

EDIT:

Related topics