ModeSMixer2

[laxlou]

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.

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

[Anmer]

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.

[laxlou]

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.

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

[Anmer]

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

[laxlou]

Where 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

[Anmer]

Can you access the SD card in the FR24 receiver?

[laxlou]

Can 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.

[Anmer]

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.

[Anmer]

This is the response I got from FR24.

Maybe contact FR24 Support?

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

[laxlou]

This is the response I got from FR24.

Maybe contact FR24 Support?

We 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