Help troubleshoot fr24feeder not working

[MerNion]

Some help please. It stopped working for some reason all of a sudden some days ago.

2023-04-13 19:33:14 | ______ _ _ _ _ _ _____ ___
2023-04-13 19:33:14 | | ___|| |(_) | | | | | | / __ \ / |
2023-04-13 19:33:14 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2023-04-13 19:33:14 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2023-04-13 19:33:14 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2023-04-13 19:33:14 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2023-04-13 19:33:14 | __/ |
2023-04-13 19:33:14 | |___/
2023-04-13 19:33:14 | [main][i]FR24 Feeder/Decoder
2023-04-13 19:33:14 | [main][i]Version: 1.0.34-0/generic
2023-04-13 19:33:14 | [main][i]Built on Jan 10 2023 10:02:35 (decoder-v1.0.34-0-7c5301b.git/Linux/static_armel)
2023-04-13 19:33:14 | [main][i]Running on: debian="9"
2023-04-13 19:33:14 | [main][i]Local IP(s): 192.168.0.109,fe80::6b14:3076:4439:6ebd
2023-04-13 19:33:14 | [main][i]Copyright 2012-2023 Flightradar24 AB
2023-04-13 19:33:14 | [main][i]https://www.flightradar24.com
2023-04-13 19:33:14 | [main][i]DNS mode: PING
2023-04-13 19:33:14 | [main][i]Automatic updates are ENABLED
2023-04-13 19:33:14 | 23-04-13 19:33:14.737 [E][:] Local time: 2023-04-13 19:33:14 +0300
2023-04-13 19:33:14 | 23-04-13 19:33:14.745 [E][:] GMT+0 time: 2023-04-13 17:33:14 +0300
2023-04-13 19:33:14 | 23-04-13 19:33:14.745 [E][:] Your machine should be set as GMT+0 time zone!
2023-04-13 19:33:14 | 23-04-13 19:33:14.749 [W][:] Time zone is not set to GMT+0
2023-04-13 19:33:14 | 23-04-13 19:33:14.749 [I][http-server.cpp:270] [httpd]Server started, listening on :::8754
2023-04-13 19:33:15 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2023-04-13 19:33:15 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2023-04-13 19:33:15 | [master][i]Starting processing thread
2023-04-13 19:33:15 | [main][i]Reader thread started
2023-04-13 19:33:15 | [reader][i]Initializing reader
2023-04-13 19:33:15 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://192.168.0.7:30006)
2023-04-13 19:33:16 | [reader][i]Connected to the receiver, configuring
2023-04-13 19:33:16 | [reader][i]Configured, processing messages
2023-04-13 19:33:16 | [time][i]Synchronizing time via NTP
2023-04-13 19:33:16 | [time][i]Time synchronized correctly, offset +0.002 seconds
2023-04-13 19:33:16 | [feed][i]Downloading configuration
2023-04-13 19:33:16 | [main][i]Feed Network client started
2023-04-13 19:33:16 | [feed][d]fetching configuration
2023-04-13 19:33:16 | [raw][i]Initializing server
2023-04-13 19:33:16 | [main][i]RAW data server started
2023-04-13 19:33:16 | [raw][i]Starting server on :::30334
2023-04-13 19:33:16 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-VALIDATED
2023-04-13 19:33:16 | [feed][i]configuring decoder
2023-04-13 19:33:16 | [feed][c]Max range AIR: 350.0nm
2023-04-13 19:33:16 | [feed][c]Max range GND: 100.0nm
2023-04-13 19:33:16 | [feed][i]configuration changed
2023-04-13 19:33:16 | [feed][i]defined 3 servers
2023-04-13 19:33:16 | [feed][c]Timestamps: optional
2023-04-13 19:33:16 | 23-04-13 19:33:16.945 [E][:] Local time: 2023-04-13 19:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.945 [E][:] Local time: 2023-04-13 19:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [E][:] GMT+0 time: 2023-04-13 17:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [E][:] Your machine should be set as GMT+0 time zone!
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [W][:] Time zone is not set to GMT+0
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [E][:] GMT+0 time: 2023-04-13 17:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [D][receiver_ac_sender.cpp:141] Stop called on non-running network thread for feed
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [E][:] Your machine should be set as GMT+0 time zone!
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [W][:] Time zone is not set to GMT+0
2023-04-13 19:33:16 | 23-04-13 19:33:16.953 [I][crxstats.cpp:588] [stats]Stats thread started
2023-04-13 19:33:16 | 23-04-13 19:33:16.957 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: FEED_NAME_HERE, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
2023-04-13 19:33:16 | 23-04-13 19:33:16.965 [E][:] Local time: 2023-04-13 19:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.965 [E][:] GMT+0 time: 2023-04-13 17:33:16 +0300
2023-04-13 19:33:16 | 23-04-13 19:33:16.965 [E][:] Your machine should be set as GMT+0 time zone!
2023-04-13 19:33:16 | 23-04-13 19:33:16.965 [W][:] Time zone is not set to GMT+0
2023-04-13 19:33:16 | 23-04-13 19:33:16.965 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed FEED_NAME_HERE
2023-04-13 19:33:16 | [feed][n]FEED_NAME_HERE@185.218.24.22:8099/UDP
2023-04-13 19:33:16 | [feed][n]connecting
2023-04-13 19:33:17 | [feed][n]connected via UDP (fd 33)
2023-04-13 19:33:17 | [feed][n]working
2023-04-13 19:33:47 | [feed][n]ping 1
2023-04-13 19:33:48 | [feed][n]syncing stream result: 1
2023-04-13 19:34:17 | [feed][n]ping 2
2023-04-13 19:34:18 | [feed][n]syncing stream result: 1
2023-04-13 19:34:47 | [feed][n]ping 3
2023-04-13 19:34:48 | [feed][n]syncing stream result: 1
2023-04-13 19:35:17 | [feed][n]ping 4
2023-04-13 19:35:18 | [feed][n]syncing stream result: 1
2023-04-13 19:35:47 | [feed][n]ping 5
2023-04-13 19:35:48 | [feed][n]syncing stream result: 1
2023-04-13 19:36:17 | [feed][n]ping 6
2023-04-13 19:36:18 | [feed][n]syncing stream result: 1
2023-04-13 19:36:47 | [feed][n]ping 7
2023-04-13 19:36:48 | [feed][n]syncing stream result: 1
2023-04-13 19:37:17 | [feed][n]ping 8
2023-04-13 19:37:18 | [feed][n]syncing stream result: 1
2023-04-13 19:37:47 | [feed][n]ping 9
2023-04-13 19:37:48 | [feed][n]syncing stream result: 1
2023-04-13 19:38:17 | [feed][n]ping 10
2023-04-13 19:38:18 | [feed][n]syncing stream result: 1
2023-04-13 19:38:47 | [feed][n]ping 11
2023-04-13 19:38:48 | [feed][n]syncing stream result: 1



pi@raspberry:~ $ fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2023-04-13 16:42:25.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-FEED_NAME_HERE.
[ ok ] FR24 Tracked AC: 0.
[ ok ] Receiver: connected (236 MSGS/0 SYNC).
[FAIL] FR24 MLAT: not running ... failed!

What does the "236 MSGS/0 SYNC" mean??? Any ideas why it is not tracking the planes? I have selected AVR tcp and port 30006 which output raw data (selected yes). I selected AVR because the SBS1 tcp for some reason it is not working eventhough it is an sbs1 receiver.

[Oblivian]

I'm surprised it worked before at all

1.0.29-10] - 2022-06-13 ## Removed
- POS-3279 Remove SBSx via Basestation option from fr24feed

I expected it wont recognize any tcp data there. It needs to know it's an sbs which is proprietary

https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/9479-fr24feed-uploader-additional-info?p=89287#post89287

That means using usb and identity the port properly using lsusb

https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/9479-fr24feed-uploader-additional-info?p=146599#post146599

[MerNion]

It did work, strange... Will read the thread for my options.. Thanks!

[MerNion]

I'm surprised it worked before at all

1.0.29-10] - 2022-06-13 ## Removed
- POS-3279 Remove SBSx via Basestation option from fr24feed

I expected it wont recognize any tcp data there. It needs to know it's an sbs which is proprietary

https://forum.flightradar24.com/foru...9287#post89287

That means using usb and identity the port properly using lsusb

https://forum.flightradar24.com/foru...599#post146599

I need some help, i can't figure it out..

You say:

SBS1
Configure FR24feed for SBS1(USB)
Enable 'SBS Feed' (relay out)
Close FR24feed

Configure Basestation for network data with the source of
IPofPI:20072
Close

Run FR24feed - check connect via USB to SBS OK

Open basestation - check connect to fr24feed output on 20072 as intended + displays

I am running fr24feed on rpi via a Vmware machine and I have selected SBS1/1e (USB) but it says it is not connected.. I also tried the baud rate at default or 921600 and still not working..

Thanks

I get this in the log:

[reader][i]Connecting to SBS1 receiver via USB (/dev/ttyUSB0)
[reader][i]Connected to the receiver, authenticating
[reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver

[Oblivian]

Did you use lsusb and confirm it can attach? And is actually ttyusb0 (and it's case sensitive)

I very much doubt the usb port is that high. 3mbps is usually the maximum

Also, you're adding additional hoops using a vm. It requires approval and ensuring it is passing through usb devices and so on

In all honesty I don't own one, and there are literally no SBS users that ever post here with their experiences even after they use to come for help to confirm how they got it working no matter how much I asked to share

https://forum.flightradar24.com/forum/radar-forums/sbs-1-sbs-3-and-basestation

All the instructions are hearsay based on fragments of info from users and bit by bit FR are seemingly dropping support

The data that comes out of them is proprietary and something else to deal with.

Fr24 support email may be your only option to confirm they still even work. But good luck. They don't bother with the forum unless someone complains or they seeming come looking for solutions themselves outside the scripted replies.

[Oblivian]

Also sanity check it still receives in basestation windows too... That at least will confirm the hardware and usb speed.

[Oblivian]

Or ditch connection using fr24feed totally and get something else to manage it

https://radarspotting.com/forum/index.php?topic=15775.0

[abcd567]

Install ModeSMixer2 and use it to receive data from SBS on port 30006, convert it and output it to Beast port 30005 for use by FR24

Here is what Sergesero (author of ModeSMixer2) has posted.
https://forum.flightradar24.com/foru...6045#post56045


ModeSMixer2 is no more available at Sergesero's Google drive as he has abandoned this project since last two years. However I had copies down loaded on my computer , which I uploaded to my githib site and also posted scripts to install it on Linux.

My Github page containing Windows and Linux versions of ModeSMixer2
https://github.com/abcd567a/mm2/releases/tag/v1

My Github page providing script for automated installation of ModeSMixer2 with Systemd support:
https://github.com/abcd567a/mm2/blob/master/README.md


.

[MerNion]

Also sanity check it still receives in basestation windows too... That at least will confirm the hardware and usb speed.

Basestation does work normally when I open it up (when I don't have the USB binded to the VMWare to use it on fr24feed).

Did you use lsusb and confirm it can attach? And is actually ttyusb0 (and it's case sensitive)

I very much doubt the usb port is that high. 3mbps is usually the maximum

Also, you're adding additional hoops using a vm. It requires approval and ensuring it is passing through usb devices and so on

sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 19.171892] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0

I have tried every Receiver option on fr24feed that has USB support (Modes beast usb/serial, sbs1/e usb sbs3 usb, microadsb usb, AVR usb/serial) with all possible baudrate options (57600, 115200, 921600, 1Mbit, 3Mbit) and none works.

I will try and see what this ModeSMixer2 is and how can I use it. Do I just run it from the windows command line while Basestation is running and it will read the port 30006 data and output it to 30005 as beast? Then select modesbeast TCP from fr24feed and use that as the source?

[Oblivian]

My advice, doodle the heck out of a bit of paper incl port in/out. Making sure the flow doesn't have multiple identical ports open etc.

Modesmixer is that, it can mix Multi format stuff in and spit it out in different formats/ports. Easy to enable fr24 outputs and have them open from that too causing conflict. Shut them all to start with and plot the flow.

[MerNion]

The flow is like that:

SBS1 Hardware ----> USB Connection to PC ----> Windows (This config is working as Basestation immediately works when fired up, but there is no fr24feed windows application)

Since fr24feed only runs on RPI or linux machines, I have to use VMWare anyway.. Is there an alternative?

[MerNion]

Wait, i am lost with all these options... If I run Basestation on my windows, it spits out on 30003 this kind of data:

MSG,3,137,7,3964E8,1705693,2023/04/24,10:25:18.437,2023/04/24,10:25:19.263,,34575,,,37.64531,22.75197,,,0,0,0,0
MSG,3,137,7,3964E8,1705693,2023/04/24,10:25:18.853,2023/04/24,10:25:19.263,,34550,,,37.64484,22.75328,,,0,0,0,0
MSG,4,137,7,3964E8,1705693,2023/04/24,10:25:19.055,2023/04/24,10:25:19.263,,,482.8,113.4,,,-2752,,,,,
MSG,4,137,835,468644,1705696,2023/04/24,10:25:18.639,2023/04/24,10:25:19.263,,,78.1,129.8,,,0,,,,,
MSG,8,137,835,468644,1705696,2023/04/24,10:25:18.639,2023/04/24,10:25:19.263,,,,,,,,,,,,0
MSG,3,137,835,468644,1705696,2023/04/24,10:25:18.853,2023/04/24,10:25:19.263,,5400,,,37.78631,23.30463,,,0,0,0,0

Can't fr24feed which i run on vmware connect with tcp to host computer at 30003 and read that?

[MerNion]

FINALLY!!!!

ModeSMixer2 did the trick!!

The configuration of modesmixer2 on Windows computer which is running Basestation.
--inConnect 192.168.0.7:30003 --outServer beast:33033

Then on the VMWare debian which runs fr24feed I selected ModeS Beast (TCP), 192.168.0.7:33033

and BOOOM!!

[abcd567]

Glad to know your problem is solved by ModeSMixer2.


This is how I run it. can configure fr24 as
host="IP of Windows Computer Running ModeSMixer2:30005"


2-ModeSMixer2.png



2-ModeSMixer2-config.png



2-FR24 Settings.png






2-Basestation Software.png


2-ModeSMixer2-Map and Graph.png




Please see another screenshot in next post, as forum does not allow attaching more than 5 images per post.



.

[abcd567]

Continued from previous post, as attaching more than 5 images per post is not allowed.

HOW TO:
ModeSMixer2 Windows Batch File - One item per line format
Uses ^ (Caret) at end of lines.

2-ModeSMixer2Config - One item per line.png