SBS-3 Connection issues during setup

[skippyinspace]

Im in the proccess of setting up the following

SBS 3 - USB Connection
Pi 3+

Have down load the image to the pi and extracted , No other adbs software on the pi.

Have got to step 4.3 Enter your recievers Com port and path and getting this error - Entered Path, 2, does not exist in the file system or is inaccessable

From the SBS 3 I have a port of 10001 a NEMA port of 30007.

Am I missing something, Is there a setting in the SBS 3 Base station software I need to change,? Is there a path that I should be entering? I feel as though Im missing something very obvious.

If Im using the wrong settings where do I find the correct ones.

Thanks
Ian
Peterhead
Scotland

[Oblivian]

'2' is not valid in unix land

See lusb commands to query port.

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

[skippyinspace]

Thanks for that. Seems to have worked, But since its 11.30pm and ABZ curfew is in place probbably wont be for a few hours until I see any uploads.

[skippyinspace]

Sorry for the posts but If Someone can break something its me!

Ive always had some sort of problem with not understanding the Network connections even before trying to connect to FR24.

I think it has something to do with the com directory path from option 4.3 looking at the logs - Any help would be appriciated Thanks Ian

The SBS3 is connected to the pi via USB.

The Lights on the USB are
Power - Red
USB - Orange
Sesson Active - No Light
Nvram No Light
Auxilary - No Light
Ethernet - No Light
Tri Colour No Light
Signal 1 - Blu
Signal 2, 3 and 4 Occasionaly Blue

My Settings from the Pi UI

image.png
My Log File

2024-01-01 10:06:22 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:22 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:06:19 | [feed][n]syncing stream result: 1
2024-01-01 10:06:18 | [feed][n]ping 79
2024-01-01 10:06:17 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:17 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:06:12 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:12 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:06:07 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:07 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:06:02 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:06:02 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:05:57 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:05:57 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:05:52 | [reader][e]Could not connect to /dev/ttyUSB0
2024-01-01 10:05:52 | [reader][i]Connecting to SBS3 receiver via USB (/dev/ttyUSB0)
2024-01-01 10:05:49 | [feed][n]syncing stream result: 1
2024-01-01 10:05:48 | [feed][n]ping 78


Thanks Ian

[Oblivian]

Please don't make a new thread for every single query about the same process setting up/establishing a feeder.

• Did you simply copy/paste the /dev/ttyUSB0 or actually run lsusb /dmesg to find and confirm the one in use.
• Is it actually a SBS3
• Don't turn on all the SBS relay/Raw/Decoded (you have yes to all 3 currently)

As some of those don't actually work when using an SBS device.

Basically you are almost on your own. With every new version of the feed software they seem to take away more and more kinetic options. It is heavily proprietary data streams.

So most don't bother anymore.

Or if they do, they use a 3rd party package to connect to it and do the work and provide everything else beast format over TCP.

https://discussions.flightaware.com/t/can-i-use-a-kinetic-sbs-3-with-a-pi/88266

[skippyinspace]

Apolgies as I thought these were seperate issues.

To answer your questions

1) Yes it is connected to the pi via the usb (or I assume so as a cable goes from the Pi to the pi USB port to the SBS 3)
2)Yes I did paste it Sudo lusb gives the following
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


3) Yes its an SBS 3 - Bought noy long after they came out

4) Will switch these to no or should any be a yes?

Thanks for the help again.

Ian