ModeSMixer2 with USB?

[DaveReid]

Further update (of sorts):

I managed to persuade the FTDI drivers to load eventually on my W7 machine, so Device Manager now shows a "USB Serial Port" (2 of them, in fact!) with speeds up to 921600 baud.  My terminal program will happily capture the SBS-1 (non-Ethernet) API output on the appropriate COM port.

But still no joy with ModeSMixer2 on the W7 box, though I haven't yet tried all the versions, so one might work.  Next step is to examine the debug logs from BaseStation on both the W10 and W7 machines to see if there are any obvious differences in the login sequence.

I haven't tried the SBS-3 on the W7 box yet, either, so that's on the list too.

[IanH]

Only just noticed this thread.

There are differences as to how MM2 sees the SBS-1 and SBS-3 via IP as shown from this thread. https://radarspotting.com/forum/index.php?topic=2978.msg55964#msg55964

May also be the case for RS232?

If I have time, might just get my SBS-1e out of the cupboard to check.

Hated all the parameters for RS232 - still got a break-out box for DB-25 connectors. Never going to use it again but still I keep it.

[HellG]

Hi,
any news about how to connect with MM2 to a SBS-1 via USB? While sbs1xxx on Linux works right out of the box and sets the serial device to

Code Select Expand

stty </dev/ttyUSB1
speed 921600 baud; line = 0;
min = 0; time = 2;
-brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke
MM2 only tries to connect, but nothing more:

Code Select Expand

2023-09-13 14:42:53.434  INFO    ModeSMixer2 v.20190413
2023-09-13 14:42:53.444  INFO    inSerial(/dev/ttyUSB1:921600) connected
^C2023-09-13 14:42:57.742  DEBUG    AirInfo::close()
2023-09-13 14:42:57.791  DEBUG    AirInfo::close()
2023-09-13 14:42:57.792  INFO    Closed successfully
Unfortunately I have no sbs1xxx for Raspberry Pi so that I can't test it, but I would really like to use MM2 with my SBS-1.

[Anmer]

Welcome.

Can I ask what setup you want to achieve with ModeSMixer2?

What's decoding the message data for you at this time?

[HellG]

I would like to build a standalone independent networked ADSB receiver with a minimum footprint with my existing SBS-1 (already from 2006, but still working!). I once had this working with a Seagate Dockstar and sbs1xxx but this setup is long gone and so I tried to use a Raspberry Pi 3 for this task. I need the aircraft position accessible via network to pre-position a high-gain telemetry antenna. Fine tracking is then done by the telemetry system itself. I managed to get fr24feed running, but I am not sure if this works without internet access. If it does I am probably done as I can access tracking data from one of the network ports fr24feed provides. Or is it possible to connect ModeSMixer2 to one of these protocols, so I have the web interface and the various output protocols?

PS: I just checked the ModeSMixer2 thread and it should be possible to access the received data on one of the ports fr24feed can provide. The only question remaining is if fr24feed also runs without internet connection.

[Anmer]

Thanks.  If I understand correctly you want to use your SBS-1 as a Mode-S receiver and run ModeSMixer2 on an RPi to make decoded data available on your local network?  But you want to connect the SBS-1 to the RPi using USB?

Did you test this setup?

[HellG]

Thanks.  If I understand correctly you want to use your SBS-1 as a Mode-S receiver and run ModeSMixer2 on an RPi to make decoded data available on your local network?  But you want to connect the SBS-1 to the RPi using USB?

Did you test this setup?

Correct. That was my plan. I have it running (SBS-1 connected via USB to RPi3) with fr24feed and it works also without internet connection. The decoded data is available ASCII on port 30003 and I can also connect with a BaseStation (runs very well on Linux with wine) and display the data coming in on port 20072. So at the moment it is not really necessary to run ModeSMixer2. Nevertheless I will try to run it with ModeSMixer2 also.

Does anybody know how the website MM2 provides (via --web option) is supposed to work? I can connect MM2 to fr24feed via Port 30003 and see converted traffic on another port (e.g. --outServer fatsv:30005) but even if the debug log shows many incoming messages, the website shows nothing.