I have the above and want to share data to Flight Radar 24.
Silly question is it just a case of just doing this as per the manual and making sure the SBS 3 is connected to the Pi
Installation Option 2 - A - Download our Raspberry Pi package containing everything you
need to start sharing your data with us:
ie no need to download anything else.
Plan would be to do the following when I want to see my local traffic ,
enter your radar ID in the Radar filter to view just the aircraft you're tracking on the live Flightradar24 map.Yes, enter your radar ID in the Radar filter to view just the aircraft you're tracking on the live Flightradar24 map.
Thanks in advance
Ian
Do you only want to share the data to FR24 or do you want to use it elsewhere, such as for Basestation or VRS and maintain a local database of received aircraft data?
Only FR24
I have downloaded the image and atempted to connect but though its saying online its not feeding the data to FR24.
Looks like a path issue or something.
2024-01-01 10:06:22 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:22 | [reader]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:06:19 | [feed][n]syncing stream result: 1
I have a post on the FR24 Forum under feeding data forum page.
Though Im looking for the simplest way to run the system 24/7 and share data where I can see it.
I dont have anything else on the pi like, Dump 1090 or mixmodes2 Though a forum suggestion was to instal mixmodes2 or even buy a dongle
Ian
The SBS-3 has raw data output avilable via Ethernet on port 30006.
The FR24 manual has more information on sharing data from the SBS, page 8 onwards:
https://repo-feed.flightradar24.com/fr24feed-manual.pdf
Sorry for bieng a bit slow here.
Does that mean plugging the ethernet cable from the SBS 3 direct into the Pi (Removing the USB Cable) and then do I chose SBS via Ethernet / TCP and use the setting in the FR24 manual you refer to.
Thanks
Ian
Unfortunately I'm not setup to run any tests so this is not a guaranteed solution.
The FR24 manual sstates the SBs-3 can be connected to the RPi via Ethernet or USB. Whichever you try, you need to edit the config file. Appendix A should help.
Getting this now from the log
2024-01-01 17:43:01 | [reader][e]Could not connect to 192.168.1.170
2024-01-01 17:42:57 | [reader]Connecting to SBS3 receiver on 192.168.1.170:10001
2024-01-01 17:42:52 | [reader][e]Could not connect to 192.168.1.170
2024-01-01 17:42:49 | [reader]Connecting to SBS3 receiver on 192.168.1.170:10001
2024-01-01 17:42:44 | [reader][e]Could not connect to 192.168.1.170
2024-01-01 17:42:41 | [reader]Connecting to SBS3 receiver on 192.168.1.170:10001
2024-01-01 17:42:36 | [reader][e]Could not connect to 192.168.1.170
Settings
Host/IP: 192.168.1.170:10001
How is the sbs connected to the RPi, USB or Ethernet?
Can you post the FR24 config file?
Quote from: skippyinspace on January 01, 2024, 05:17:28 PMDoes that mean plugging the ethernet cable from the SBS 3 direct into the Pi
No, both the Pi and the SBS-3 need te be connected to a switch. Most modems/routers come equipped with such a switch.
Silly question where do I find the FR24 config file, I always strugle trying to find things on the pi!
Ok as for the Ethernet cable I do have a switch but again excuse my no understanding I plug from the Pi into the switch and then from the switch into the SBS 3 - Why escpecially as the switch wont be connected to anything else.
I do understand though if using ethernet then the USB must be plugged in as it is also part of the power source.
I did try to post the FR24 web UI but I couldnt work out how to!
Thanks
Found the config file
receiver="sbs3tcp"
fr24key="7f351959ae484b83"
host="192.168.1.170:10001"
path="/dev/ttyUSB0"
bs="yes"
raw="no"
baudrate="3000000"
logmode="1"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="yes"
mlat-without-gps="yes"
Try connecting the SBS-3 to the RPi using USB and change:
receiver="sbs1usb"
If that still doesn't work, additionally try:
host="192.168.1.170:30006"
Made both changes now getting this error, Which goes back to the I have no idea what to put in the com/ dev path and took the info from a post.
2024-01-02 09:43:39 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-02 09:43:39 | [reader]Connecting to SBS1 receiver via USB (/dev/ttyUSB0)
2024-01-02 09:43:34 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-02 09:43:34 | [reader]Connecting to SBS1 receiver via USB (/dev/ttyUSB0)
2024-01-02 09:43:29 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-02 09:43:29 | [reader]Connecting to SBS1 receiver via USB (/dev/ttyUSB0)
2024-01-02 09:43:24 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-02 09:43:24 | [reader]Connecting to SBS1 receiver via USB (/dev/ttyUSB0)
2024-01-02 09:43:22 | [feed][n]syncing stream result: 1
2024-01-02 09:43:21 | [feed][n]ping 3
When I change the dev/ttyusb to either 1 or 2 I get the below
2024-01-02 12:11:11 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-02 12:10:51 | [reader]Connected to the receiver, authenticating
2024-01-02 12:10:51 | [reader]Connecting to SBS1 receiver via USB (/dev/ttyUSB1)
2024-01-02 12:10:46 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-02 12:10:43 | [feed][n]syncing stream result: 1
Further info
sudo lsusb
Bus 001 Device 009: ID 0403:6010 Future Technology Devices International, Ltd FT2232C/D/H Dual UART/FIFO IC
Bus 001 Device 006: ID 045e:00b0 Microsoft Corp. Digital Media Pro Keyboard
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Running
Sudo lsusb /dmseg (Gives below )
Usage: lsusb [options]...
List USB devices
-v, --verbose
Increase verbosity (show descriptors)
-s [[bus]:][devnum]
Show only devices with specified device and/or
bus numbers (in decimal)
-d vendor:[product]
Show only devices with the specified vendor and
product ID numbers (in hexadecimal)
-D device
Selects which device lsusb will examine
-t, --tree
Dump the physical USB device hierarchy as a tree
-V, --version
Show version of program
-h, --help
Show usage and help
Thanks for your paitence
Ian
Quote from: skippyinspace on January 01, 2024, 07:18:16 PMWhy escpecially as the switch wont be connected to anything else.
Both the Pi and the SBS-3 are what are in network terms called 'hosts'. That means they send and receive data via the same wire in the cable. Hosts need to 'talk' to a 'node'. The switch is such a node. That device make sure that the data that is send via the tx-wire arrives on other host's rx-wire and vice versa. The only way to let two hosts communicate directly is by using a 'cross-cable'. In such a cable the tx and rx wires are crossed between the two connectors.
Thanks for the explanation about the swithch. Ive been talking to FR24 Support who are working on this via the USB side of things so asked me to remove the host IP address
Have changed the USB from USB0 to USB1 and now get the following, I am talking to Support but again feel like im missing something obvious.
2024-01-03 16:38:17 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-03 16:38:14 | [feed][n]syncing stream result: 1
2024-01-03 16:38:13 | 24-01-03 16:38:13.946 [crxstats_sender.cpp:84] [stats]sent 16 bytes
2024-01-03 16:38:13 | [feed][n]ping 20
2024-01-03 16:38:13 | [reader]Connected to the receiver, authenticating
2024-01-03 16:38:13 | [reader]Connecting to SBS3 receiver via USB (/dev/ttyUSB1)
2024-01-03 16:38:08 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-03 16:38:05 | [reader]Connected to the receiver, authenticating
2024-01-03 16:38:05 | [reader]Connecting to SBS3 receiver via USB (/dev/ttyUSB1)
2024-01-03 16:38:00 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-03 16:37:56 | [reader]Connected to the receiver, authenticating
2024-01-03 16:37:56 | [reader]Connecting to SBS3 receiver via USB (/dev/ttyUSB1)
2024-01-03 16:37:51 | [reader][e]Authentication failed, please make sure the specified device is a SBSX-USB receiver
2024-01-03 16:37:46 | [reader]Connected to the receiver, authenticating
2024-01-03 16:37:46 | [reader]Connecting to SBS3 receiver via USB (/dev/ttyUSB1) zz0.a4qovy0a4sdzz
Copy on ini file
receiver="sbs3usb"
fr24key="7f351959ae484b83"
path="/dev/ttyUSB1"
bs="yes"
raw="yes"
baudrate="921600"
logmode="1"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="no"
mlat-without-gps="no" zz0.3j9yxxfl047zz
�������
Have you tried this config?
receiver="sbs1usb"
fr24key="7f351959ae484b83"
host="192.168.1.170:30006"
path="/dev/ttyUSB0"
bs="yes"
raw="no"
baudrate="3000000"
logmode="1"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="yes"
mlat-without-gps="yes"
Was told ny FR24 Support to remove the IP address if using USB. In the end I did trial and error and it suddenly workerd. It looks like iy was the baud rate that was the sticking point. Used the 1mb mode S Beast and the SBS Feed = Yes
Thanks for the help
Ian
Great, pleased to hear you're up an running.
FR24's manual is a bit confusing:
sbs1usb - SBS1, SBS1er, SBS3 connected directly via USB. For Linux users the device
path of the receiver needs to be specified using "--path" (see below). When using a
Kinetic Avionics receiver an additional option "--mpx" is available so you can
connect to BaseStation as well.
For the benefit of others, can you share the full config file that now works.
Well I VNC into the PI and other than closed a control box that was open and then lost internet and now it doesnt work again!
Will now leave it until Im back from work
Starting to get anoyed !
Starting to think MM2 might be the way to go but this is a foreign language to me, If this could be explained in some sort of English
From an old post
Below is the the code that I use to link a Pi to my SBS-3. I have also added a docker compose file used to create a container which as mm2 pre-installed into it and the necessary parameters to get it working with the SBS-3. The code outputs Beast/AVR format on port 30005, Basestation format on 30003 and SBS10001 format on port 10002, the website port of mm2 is set to 6081.
CodeSelect
/usr/local/bin/modesmixer2 --inSerial /dev/ttyUSB1:3000000:none --outServer beast:30005 --outServer msg:30003 --outServer sbs10001:10002 --web 6081 --location XXXXX:YYYYYY
Docker compose for mm2 with SBS-3 as a usb input.
CodeSelect Expand
mm2BS:
image: mikenye/modesmixer2:latest
tty: true
container_name: mm2BS
privileged: true
restart: always
devices:
- /dev/bus/usb:/dev/bus/usb
environment:
- MM2_WEB=6081
- TZ=${FEEDER_TZ}
- MM2_LOCATION=${FEEDER_LAT}:${FEEDER_LONG}
- MM2_INSERIAL=/dev/ttyUSB1:3000000:none
- MM2_OUTSERVER=beast:30005;msg:30003;sbs10001:10002
ports:
- 30005:30005
- 30003:30003
- 10002:10002
- 6081:6081
Have you given up on your original setup that was orking yesterday?
I havent given up yet but thought I might start investigating an alternitive.
FR24 Suport today says this the is it an SBS reciever seems to be a problem with the 64 bit image and SBS.
The thing is that FR24 Support is one email a day.
I have tried the settings again and it doesnt work, No idea why it worked yesterday!
You could try re-installing with a 32-bit Raspberry Pi OS (I think that Bullseye is the most recent) and then try all this again. IF it is still a problem then at least you can rule out the 64 bit OS being the root of the issue - this would seem odd if it was working and now is not, but you won't know unless you try :)
As its a Pi3b+ I got a new SD Card and flashed the legacy imange. Still didnt work, tried a few trial and error setting still nothing. Went had dinner and unplugged the power usb on the Y usb going into the pi. Caame back and it was working (No idea why) the ini file below
receiver="sbs3usb"
fr24key="1234xxxxxx"
path="/dev/ttyUSB1"
bs="no"
raw="no"
baudrate="1000000"
logmode="1"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="yes"
mlat="no"
mlat-without-gps="no"
AAHHHHHHHHHHHHH,
Came home and its stopped. have restarted etc and no session, Psibbly an internet drop between the wifi extender that the Pi is connected to or the extnder and the router. But I dont get why even after restarting it doesnt connect.
The Pi3b+ powersupply doesnt seem to be a tight fit into the pi scocket so Im wondering if there is an issue there.
Another of these projects that should be using what is lying around that now looks to be costing £30 or so with new power supplies, SD Cards etc.
And its back!
Think the key is possibly when it loses connection to restart everything and also to VNC into the Pi and start from the cmd prompt and wait half an hour or so!