Radarspotting

Is there a guide to setup Basestation to receive data from raspberry pi ?

help appriciated

There's no Guide here but it's quite easy.  I assume you're running a RPi with an SDR connected?

Basically you need to use ModeSMixer2 as "middleware" to get data from the RPi decoding software and make it available in BasseStaion format.

You can install ModeSMixer2 on the Windows PC running BaseStation.

What are you running on the RPi?

ADSB.im on Raspberrypi 4 with a rtl-sdr V3 from jetvision.

do I install on my pc or on the pi itself ?

Quote from: Dreamliner787 on March 11, 2025, 06:47:34 PMdo I install on my pc or on the pi itself ?

No, install ModeSMixer2.exe on the pC running BaseStation. Maybe create a new folder for it.

You then need to create a .txt BAT file such as this:

@echo off
CMD /c I:\MSM2\modesmixer2.exe --inConnect 192.168.1.136:30003 --filter-nocountry --outServer sbs10001:10002
exit
In the above example, my ModeSMixer2.exe is on my I drive in a folder named MSM2.  Your Bat file should replace that with your location path.

I assume ADSB.im outputs suitable data on the RPi?  For example, in the above, my RPI has a local IP address of 192.168.1.136 and suitable data is on port 30003.  Yours will be different.

In BaseStation you set the data source as Netweork and the local IP address of the PC running ModeSMixer and port 10002.

You can run ModeSMixer2 on the RPi, but you might find it easier on the PC.


.

ok I downloaded mm2 on pi4, setup seemed to go alright .

I can see my data on 192.xxx.x.xxx: 8xxx.

cannot open mm2.conf on Pi, to enter location.

Msg , Directory '/user/share/mm2' does not exist

connect host 127.0.0.1:3xxxx,error connection refused

reconnecting in xx seconds

it's doing this with mlat

Can you post your bat file contents please?

MM2 is on th Pi4

G'day Dreamliner,

Check out this posting on Radarspotting site to get MM2 up and running.

https://radarspotting.com/forum/index.php/topic,16004.0.html

Use the 32 bit version not the 64 version as per ABCD's instructions.

Apparently you need to run the 32 bit version of Bookworm O/S on the Pi4 not the 64 bit version of Bookworm. By the way, MM2 will not run on the Pi5 because only the 64 version of Bookworm is available.

hi,

I'm using the ADSB Feeder Image from adsb.im, not sure if you can use that and bookworm ?
Or does MM2 work with adsb.im image.

Why not save MMS2.exe and the bat file on the PC running BaseStation?

Wherever you place it the bat file has to be executed.

Can you post the contents of the bat file?

Quote from: Anmer on March 11, 2025, 06:38:50 PMThere's no Guide here but it's quite easy.  I assume you're running a RPi with an SDR connected?

Basically you need to use ModeSMixer2 as "middleware" to get data from the RPi decoding software and make it available in BasseStaion format.

You can install ModeSMixer2 on the Windows PC running BaseStation.

What are you running on the RPi?

Further to my earlier post, ABCD went on to help me set up MM2 on the Windows PC to get the ADSB data feed from my Pi5 running PiAware. I'm assuming that this setup will also run on a Pi4.

The last Windows version of MM2 that Sergsero released was 20190413. If you don't already have it, can be downloaded from ABCD's github site -

https://github.com/abcd567a/mm2/releases/download/v1/modesmixer2_windows_20190413.zip

I then unzipped this into a new folder in C:/ drive named ModesMixer2.

Copied the modesmixer2_example.bat file and renamed it MM2.bat file and edited it to something like this:-

@echo off
cmd /c c:/MM2/modesmixer2.exe --web 8888 --location -33.00:150.00 --inConnect 192.168.x.xx:30005 --inConnectId 192.168.x.xx:30105:MLAT --outServer sbs10001:10001 --outServer msg:30003 --outServer beast:31001 --outServer msg:30003 --valid-modes 0:5
PAUSE
exit

What this does is connect MM2 to your Pi's IP address (192.168.x.xx) that's running PiAware and takes the ADSB feed from port 30005 and MLAT feed from 30105 to your BaseStation port 10001. In BaseStation, in the settings option>Hardware Settings>Network, make sure 127.0.0.1 is in address and 10001 in port boxes. BTW I'm using the FlightAware blue dongle. Best to start the MM2.bat software first before BaseStation.

I, and sure others, owe ABCD and Anmer a big vote of thanks for all their hard work behind the scenes in helping us to enjoy this hobby.

To add to Oldfella's latest post.

• On what port does ADSB.im output the quivalent data to PiAware's port 30005?
• Please post your contents of the MMS2 bat file which must always be executed to provide the data for BaseStation
• This (https://radarspotting.com/forum/index.php?msg=115691) post may help.  Check the IP address for the RPi running ADSB.im

port 30005 as far as I'm aware,

downloaded ModeSMixer2 from, Downloads: ModeSMixer2 for Raspberry Pi 4,
the download contains 3 files , License.MIT, modesmixer2 and modesmixer2.txt, is that correct?

OK, let's focus on how to use MMS2.

The file modesmixer2.exe is the software that we want to use. 

If you use Windows, download the file and place it in a folder of choice.

To use the software, you need to create and launch a bat file.  When launched (opened) the bat file will communicate with the exe file and execute the bat file instructions, an example of which I posted earlier.

On its own, modesmixer2.exe is inactive.  It's the bat file that does the work and must always be running if you want to access the RPi data.

CMD /c I:\MSM2\modesmixer2.exe --inConnect 192.168.1.136:30003 --filter-nocountry --outServer sbs10001:10002
exit
In the above example, my modesmixer2.exe is on my I drive in a folder named MSM2.  Your Bat file should replace that with your modesmixer2.exe location path and RPi IP address and port (for inConnect).

My bat file is a text file created in Notepad and named "MMS2.bat".  It can be named whatever you prefer but needs to be saved as a .bat.

To launch the bat file just double click on it.  Mine is on the desktop.

I'm sure there's an option to do all this on the RPi but I have no experience of this so someone else will have to advise.

ok ,thank you , but the ModeSMixer2.exe wasn't in the folder I created for MSM2 and I downloaded that from this website.

Quote from: Anmer on March 12, 2025, 07:32:05 AM

• On what port does ADSB.im output the quivalent data to PiAware's port 30005?

30003 SBS output
30005 beast output
31005 mlat results beast output

Pretty much the same you would get from piaware.
Except the mlat results will be combined from whichever aggregators that are configured and provide MLAT results.

Quote from: Dreamliner787 on March 12, 2025, 11:28:02 AMok ,thank you , but the ModeSMixer2.exe wasn't in the folder I created for MSM2 and I downloaded that from this website.

The downloaded modesmixer2.exe file should be placed in the folder you created. It won't get there on its own.

Please post the contents of your .bat file.

CMD /c I:\MSM2\modesmixer2.exe --inConnect 192.168.1.108:30005 --filter-nocountry --outServer sbs10001:10002
exit


When I downloaded MSM2 and extracted it to C:\ModeSMixer2, there is no file called modesmixer2.exe.

"The downloaded modesmixer2.exe file should be placed in the folder you created. It won't get there on its own".

where do I find if it's not in the downloaded file ?

Thanks.

Which version of ModeSMixer2 did you download?

Is that your bat file?

Do you have an "I" drive?

Below is the contents of the ModeSMixer2 for Windows Zip.

ok, sorry think I downloaded the wrong version.

Downloaded MSM2 for windows.

this is my bat file,

CMD /c:\MSM2\modesmixer2.exe --inConnect 192.168.0.108:30005 --filter-nocountry --outServer sbs10001:10002
exit

when I double click on the bat file what exactly should happen?

Thanks.

Your bat file may need amending.  If your MSM2 folder (containing modesmixer2.exe) is on your C drive, try:

CMD /c C:\MSM2\modesmixer2.exe --inConnect 192.168.0.108:30005 --filter-nocountry --outServer sbs10001:10002
exit
If the bat is correct, double clicking on the file should open a Command window such as this:

C:\MSM2>CMD /c C:\MSM2\modesmixer2.exe --inConnect 192.168.0.108:30005 --filter-nocountry --outServer sbs10001:10002
2025-03-12 15:35:14.664  INFO     ModeSMixer2 v.20190413
2025-03-12 15:35:14.665  INFO     outServer(sbs10001:10002) started
2025-03-12 15:35:14.669  INFO     inConnect(192.168.0.108:30005) connecting 192.168.0.108:30005
2025-03-12 15:35:14.676  INFO     inConnect(192.168.0.108:30005) connected
2025-03-12 15:35:14.756  INFO     inConnect(192.168.0.108:30005) BEAST data stream detected
2025-03-12 15:35:20.762  INFO     Coverage area was determined
2025-03-12 15:35:20.762  INFO     Magnetic declination calculated

That looks like you've got MSM2 running OK.

In BaseStation Settings:

Data Source -> Use Network

Hardware Settings -> Network -> Address (IP address of PC running modesmixer2.exe0 -> Port 10002

If that works your Command window should show as below.

ok, connected to SBS1 and aircraft showing.

Quote from: Dreamliner787 on March 12, 2025, 03:54:06 PMok, connected to SBS1 and aircraft showing.

Great, we got there in the end.

Hi all,

Does anybody here use FR24 receiver (with display) with mm2? I have been running that mm2 in rpi4 and noticed now that when getting data from receiver port 30003, some data is not anymore parsed properly by mm2. For example all callsigns are missing, and then looks like mode-s transmissions without position are not shown. Something have been changed because for some time ago I got all that data correctly. I have also get info that port 30003 data is not filtered by receiver side.

I have mainly used that mm2 to create globes feed to be used then with my own scripts.

--------------
regards,
Otso

Can you post a photograph of the FR24 receiver you are using?

I'm sharing data to FR24 and am using MSM2 to access data from the RPi.

Quote from: Anmer on March 13, 2025, 03:05:21 PMCan you post a photograph of the FR24 receiver you are using?

I'm sharing data to FR24 and am using MSM2 to access data from the RPi.

Hi,

I have been sharing years and original receiver had to be changed few years ago. This one have been running since then. I look some my notes and looks like on Aug 2024 data was still valid. There have been some update to system on autumn 2024, I think data which is displayed is shown bit differently comparing earlier ones. What I have not yet done is to more deeply check that raw port30003 output.

--------
Otso

Thank you.  My FR24 receiver is over 10 years old!

I have sent an email to a contact at FR24 to see if there have been any changes.

Quote from: Anmer on March 13, 2025, 03:48:40 PMThank you.  My FR24 receiver is over 10 years old!

I have sent an email to a contact at FR24 to see if there have been any changes.

I actually asked some time ago that do they have changed anything. I got reply that nothing has been changed. Just still wondering that maybe some small changes on that port standard output. This is interesting and many thanks about your help about digging this out. I can also provide more data regarding that output. The mm2 installation on rpi4 has been basically untouched during this period.

-----
Otso

Where are you viewing the port 30003 data from the FR24 receiver?

Quote from: Anmer on March 13, 2025, 04:49:38 PMWhere are you viewing the port 30003 data from the FR24 receiver?

Currently I just use that mm2 to create that Jetvision globe-s formatted data output which I am then again parsing using own Python scripts. One thing which I am wondering is that some change on that receiver port30003 output is now causing inproper output of that globes feed. When quickly looking that raw port30003 data ie. logging it via Pytty, data definitely include ID fields like this:

ID,,333,476426809,47A50D,476426909,2025/03/13,16:56:11.655,2025/03/13,16:56:11.655,NSZ2613
 
But for example this data is now never passed again into that globes output. All callsigns are not anymore displayed there. Also looks like all short MODE-S messages are not displayed properly. This lack of data can be seen also when using mm2 web statistics output.

---
Otso

Can you access the SD card in the FR24 receiver?

Quote from: Anmer on March 13, 2025, 05:11:42 PMCan you access the SD card in the FR24 receiver?

I have never done that as the receiver is maintained by FR24. My only intention is to have ability to access that port data which is actually nowadays limited to that port30003 only. For example raw binary data is not anymore available for feeders. Also for physical access to device currently is limited as I am running receiver on remote location.

OK.  You will be able to access the card but it means opening the receiver. This occurs all the time, I know as I setup Support for FR24 and FlighAware!

Unfortunately I don't have an FR24 receiver or the latest SD card image to test.

Let's see if I get a reply from FR24.

This is the response I got from FR24.

Maybe contact FR24 Support?

QuoteWe do support raw data ports but they are disabled by default. The host needs to request opening them afaik.

Quote from: Anmer on March 13, 2025, 07:12:13 PMThis is the response I got from FR24.

Maybe contact FR24 Support?

QuoteWe do support raw data ports but they are disabled by default. The host needs to request opening them afaik.

This is really interesting. I have long time since asked also that and they responded that they are not gonna open them. But if this is a case now and ie. good old raw 30005 can be opened, situation will be much better then.

Anyway in the meantime I tested here to connect that current FR24 receiver port30003 with different modesmixer2 version (running on Windows) than used in rpi4 mm2. Situation was same, and no any callsign etc. decoding.

Thanks for your reply, I will contact them once more to check this out and come back here for results.

-----
Otso

Hi,

I actually didn't get any reply to my raw port question from FR24, but few days a go I noticed that port30003 data flow seems to be back to normal like it was earlier. Looks like FR24 receiver have been got update some time ago and after that full MODE-S data with also callsigns are now properly parsed via modeSmixer.

So, I didn't made any changes to my setup, it was just running like previously.

But all good now, have to to hope that this situation will last.

-----
Otso

Glad to hear it's all OK now.  Bit disappointed that FR24 Support didn't get back to you.