PSXT- Aerowinx TCAS

[samer747]

Hello,

I need assistance please for setting up PSXT 14.5 to inject traffic into Aerowinx TCAS. In my setup I use two PC's, one is for MSFS24 & traffic..., the second PC is for PSX and all other related PSX interfacing softwares and psx.net.

Before the latest PSXT update, I had both PSXTraffic & RealTraffic (RT) Apps installed on PC1 (MSFS24) where in RT the simulator host IP is set to PC2 (PSX) and RT operating mode selected to Aerowinx, the port 10747. I was able to inject traffic in MSFS24 and also see traffic in Aerowinx TCAS display.

After the update both PSXTraffic & PSXT got combined into one app called PSXT. I selected RTapp & Aerowinx in PSXT, and in RealTraffic RT I found out the only option to link with PSXT is to change the host IP into the same PC running PSXT (PC1 MSFS24) and operating mode selected to PSXT. In this setup I'm able to inject traffic in MSFS24 but Nothing in Aerowinx TCAS.

If anybody is using the same traffic injection APPs with PSXT & RT setup able to successfully inject traffic to both MSFS24 & Aerowinx TCAS. Can you please provide some info on how to setup these Apps properly and be able to see traffic in Aerowinx TCAS matches whats showing in MSFS24.

Thanks,
Sam   

[FlyItLikeYouStoleIt]

Realtraffic app set to operating mode "Aerowinx PSX" under Settings and Display Delay "30 seconds" under Advanced Settings.

PSXT app set to "RT Direct".

The two apps work independently of each other fetching two streams of aircraft data (but the RT Pro Licence allows this) but end up synchronized because the two sims have the aircraft in the same place and the Realtraffic app display delay of 30s matches that introduced by PSXT's buffering.

The PSXT app needs to be on the same PC as MSFS2024

[samer747]

Thanks for the info.

I was previously told to use RTapp and select Aerowinx in PSXT app and that setup didnt work. I will try to use your setup as it makes more sense.
In RT where do you set the simulator Host IP to PSX computer or to the same computer thats running PSXT & MSFS24?
I have the standard license not the pro would it still work?

Regards,

[FlyItLikeYouStoleIt]

I cannot get PSXT to get data from the RT app either.

In the RT app if PSX is on the same PC use localhost, otherwise the IP address of where PSX resides.

Unfortunately I don't think the standard licence will let you run both the RT app and PSXT in direct mode at the same time.

One loophole is to set up your own ADSB receiver with a raspberry pi and RTL-SDR dongle. Pretty easy and cheap to do. If you set up a feed direct to RealTraffic then you can get a free upgrade from standard to Pro licence.

[simonijs]

I cannot get PSXT to get data from the RT app either.

Same here.

Regards, Simon

[Balt]

Let's see what I can do to support this. So you evidently have a method to send PSX's position/attitude to MSFS somehow (how?). Then, if PSXT is running, RT could connect to PSXT in PSXT mode, and all you'd need really is an additional option in the RT app that connects to PSX but for weather and traffic injection only?

Cheers

Balthasar

[FlyItLikeYouStoleIt]

The (currently most used) software that connects PSX to MSFS is Gary Oliver's PSX.NET.xxx suite https://aerowinx.com/board/index.php?msg=81309

But there are also software solutions that connect PSX to X-Plane 11/12.

So an ideal scenario would be for the Realtraffic app to connect to PSX as it does at the moment, gaining position / time of day from PSX but with the options of feeding in traffic and weather, whilst simultaneously being able to connect to either PSXT (for MSFS) or LiveTraffic (for X-Plane) to deliver traffic to those sims.

At the moment, I cannot get the Realtraffic to PSXT link to work whilst PSX is running as there seems to be competition over who gets to use port 10747.

As far as RT, PSX, LiveTraffic and XP12 is concerned, strangely I succeed on MacOs but fail on windows (where Livetraffic complains that it cannot open a UDP port on 10747 if PSX is running).

[samer747]

Unfortunately I don't think the standard licence will let you run both the RT app and PSXT in direct mode at the same time.

before latest update to PSXT I was able to connect PSXTraffic & RT app and send traffic to Aerowinx-TCAS(which is on a different PC from both PSXT&RT ) with the basic license subscription. Why would that changes now ?? The update was mandatory not optional, PSXTraffic app became unusable, I wish it was optional!!


I noticed RT app still reads the location from Aerowinx PSX and shows traffic in that airport area, when I change location in psx it changes in RT app regardless if host IP pointing to MSFS24 PC or PSX PC. RT app does communicate but doesn't inject traffic to PSX-TCAS at least in my situation.

[Balt]

The RT App caters to a whole ecosystem of data consumers, both simulators and EFBs. Traffic and weather is generally sent via UDP broadcast so any applications in the LAN wanting to consume that data can without needing a pro license.

If in "Aerowinx PSX" mode, the RT App reads aircraft position and attitude from PSX and injects the traffic and weather in the area to PSX on that same TCP connection. But: Make sure the "Disable PSX traffic injection" checkbox is not checked!

If in "PSXT (MSFS/P3D)" mode, the RT App reads aircraft position and attitude from PSXT, but does NOT inject traffic on that connection, it only sends traffic and weather via UDP broadcast. What might be confusing is that the RT App will appear to be working when connected to PSXT while in "Aerowinx PSX" mode because PSXT uses the same position and attitude reporting protocol as PSX.

So you need to make sure you are really connected to PSX with the RT App: Check the simulator host points at the computer where PSX is running (not PSXT), and that the RT App really is in "Aerowinx PSX" mode.

If all are running on the same host, you need to setup PSXT so it listens on a different port than PSX (10747), otherwise you may end up with both PSX and PSXT fighting over who gets to open port 10747. There's a configuration option to achieve this - check the PSXT documentation for that.

[FlyItLikeYouStoleIt]

I am still struggling. Be patient!

PSX opens port 10747 (by default) for TCP connections

When in PSX mode, RealTraffic connects to this by TCP (though this can be changed by the "Simulator Host IP" and "Port" options in Standard Settings.)

This TCP connection is two way and provides position to RT and weather / traffic to PSX from RT.

Now if "Broadcast data to third party apps" is ticked in RT, then RT does UDP broadcast to port 10747 (?) across the local subnet.

LiveTraffic and / or PSXT need to open 10747 to receive these UDP packets. If they are on the same PC as PSX then this is a problem as PSX already has grabbed 10747 for TCP.

Now you have suggested that PSXT can be configured to listen to UDP on a different port. But can RT be configured to send UDP broadcast to a different port?

At first I thought this could be fixed by making PSX use a different port and connecting RT to that instead, but on checking I find there is no way to do this.

[EDIT] Realised there is a way to make PSX use a different port through its settings files and the Port10747 parameter. Then RT can connect to PSX on eg 11747 and leave 10747 free for UDP broadcast.

[Balt]

This may indeed be a firewall issue, to sort this, I would recommend you disable any firewalls until you get it working, then re-enable them and make rules that allow the following ports to be received:

10747 (default) port is only for the TCP connection to the simulator. The UDP broadcasts are on different ports.

port 49005: Traffic in RTTFC format (used by PSXT)
port 49006: Weather (used by PSXT)

And some EFB packets:
port 49002: Traffic in XTRAFFIC format (not used by PSXT)
port 49002: on same port also Pos/Att XGPS + XATT messages
port 4000: GDL90 unicasts
port 63093: GDL90 auto discovery broadcasts (receive)

[FlyItLikeYouStoleIt]

Ah, ok. In that case the issue is that both PSXT and LiveTraffic try to open 10747 as TCP listening ports to allow RT to connect to them (even though RT may have no intention of doing so), but fail because PSX has already grabbed it.

Firewalls are not the problem.

I think I get it now. If on a single system, changing the PSX main port away from 10747 and reconfiguring all clients solves the problem.

[Balt]

...or you can change the PSXT port also:

Here's how it all works:
- RT app connects to PSX, sends traffic/weather over UDP
- Since you're not connecting to PSXT, configure PSXT to not start a server at all (and thus not use the 10747 port) by setting this in the parameters.xml:

<parameter name="PSX_SERVER_HERE" value="false" />

You can also change the port number with this entry in the parameters.xml:

<parameter name="PORT_NUMBER" value="10747" />

[FlyItLikeYouStoleIt]

Perfect. Thanks!

[samer747]

Before I started doing anything with PSXT config's. I removed RT app from the PC that has MSFS & PSXT and reinstalled it on the other PC with aerowinx PSX, once I started the RT app I saw traffic injection in PSX.

I had to change the host IP in RTapp to point to the other PC(MSFS&PSXT), in PSXT I selected RTapp.

I did a test flight, in PSX-TCAS there were 2 - 4 aircraft traffic showing but looking at MSFS scenery traffic I couldn't see those aircrafts, Not sure both apps are really linked together. In PSX i made sure the traffic selection was to external control.

[kiek]

I did a test flight, in PSX-TCAS there were 2 - 4 aircraft traffic showing but looking at MSFS scenery traffic I couldn't see those aircrafts, Not sure both apps are really linked together.

In the parameters.xml of PSXT you have to set

    <parameter name="PSX_SERVER_HERE" value="false" />

[samer747]

Thanks a lot
Wildo

[samer747]

In the parameters.xml of PSXT you have to set

    <parameter name="PSX_SERVER_HERE" value="false" />

Hello,
 
I did change server parameter to false for PSXT, restarted RTapp but no traffic came up on the screen until I changed the mode to spot and physically select the airport then re-change mode back to PSX, no psx-tcas injection at all. I did a test flight between two airports with the same setup but no PSX-TCAS through the whole flight.

I didn't play with port setup but I must change port for both PSXT & RTapp, whats a better port to use?

Did anyone else had a better luck with the setup?