PSXView with xplane12, introducing extended TCAS and real life traffic

[Victor126]

sorry but the link is on page 1

[TCASSE]

Yes on page 1

[TCASSE]

Hi Tcasse,

It works smooth as silk. Thank you!!

The altitude offset is not working for me.

Another important item would be to extract the ground speed from PSX and transmit it via PSXview to Xpilot and the Pilotedge clients.

Same for Altitude mode C

Without speed or altitude online flying is not possible. Is this something you can look into?

Ok I will plan to add ground speed and altitude. Unfortunaltely, I can not write the groundspeed dataref. The altitude from xplane is given by sim/flightmodel2/position/pressure_altitude.

Unless I am mistaken, xPilot is based on the aircraft's trajectory (latitude, longitude, altitude) and the timestamp to calculate GS/VS. Even if a "groundspeed" DataRef is modified, xPilot does not use it. As long as the PSX position is correctly injected into X-Plane, the xPilot speeds will be consistent.

If an incorrect GS is observed in xPilot, it is never a GS problem but a position update issue (update rate too low, frozen position, or lat/lon/alt desynchronization).

[Victor126]

OK thank you

[JJK]

Hi guys,

I tested yesterday an online flight with PSXView on PilotEdge and it worked partially with some work around. I used a Streamdeck with X-Keypad to transmit the transponder code as the PSXView plugin only send a 0 to Xplane. So altitude read out was working but for some reason it was also triggering the ident button constantly. And no groundspeed was send through. From what I found on the Pilotedge forum, they could accommodate for a custum data ref to pick up ground speed from PSX.
Is this something you could look into? Much appreciated all the work!

[TCASSE]

Hi guys,

I tested yesterday an online flight with PSXView on PilotEdge and it worked partially with some work around. I used a Streamdeck with X-Keypad to transmit the transponder code as the PSXView plugin only send a 0 to Xplane. So altitude read out was working but for some reason it was also triggering the ident button constantly. And no groundspeed was send through. From what I found on the Pilotedge forum, they could accommodate for a custum data ref to pick up ground speed from PSX.
Is this something you could look into? Much appreciated all the work!

For the transponder code, you need to enter the code once in PSX (could be the same code,because PSX is waiting 4 digits before displaying). I added two fictive datarefs GS et ALT that you can use by others plugins (see page 1)

[Captain_Crow]

Hi guys,
please have a look at my last Twitch.
https://www.twitch.tv/videos/2677865547
The Bird moves step by step to right. No chance to stop this.
Dataref plane path is set to "1".
best
Steff

[TCASSE]

Hi guys,
please have a look at my last Twitch.
https://www.twitch.tv/videos/2677865547
The Bird moves step by step to right. No chance to stop this.
Dataref plane path is set to "1".
best
Steff

It is neccessary to first 1. Choose a location with PSX
2. start a new flight with Xplane by selecting the same  location (or a location close to the PSX's location) then link

[Captain_Crow]

Thx Tcasse, it seems to work now...
Steff

[Snare25]

Hi TCASSE thanks a lot for all your hard work with the updates. I have tried your latest version and it is working great. I have not had time to complete a full flight yet but I have done some circuits and touch and go's and it was very smooth.
Thanks again.

[TCASSE]

Hi TCASSE thanks a lot for all your hard work with the updates. I have tried your latest version and it is working great. I have not had time to complete a full flight yet but I have done some circuits and touch and go's and it was very smooth.
Thanks again.

Thank you for your feedback I:m happy that all is good.

[JJK]

Hi Thierry,

Thanks for all the good work! PSXview, works fine now. Not sure if the Stby and ALT or C Modes  of the transponder are also being send through but maybe you can add that later.

For now I resolve that via X key pad and a Streamdeck. Ideally I would like to be able to turn of radios and xpdr from PSX altogether (like in Xview this is optionally) as I use the Saitek panel radios when flying online and with that I can use the radios of the Sparky 747.

I passed on your info on the custom data ref to Pilotedge, hopefully they can do something with it.

Best, J

[TCASSE]

Hi Thierry,

Thanks for all the good work! PSXview, works fine now. Not sure if the Stby and ALT or C Modes  of the transponder are also being send through but maybe you can add that later.

For now I resolve that via X key pad and a Streamdeck. Ideally I would like to be able to turn of radios and xpdr from PSX altogether (like in Xview this is optionally) as I use the Saitek panel radios when flying online and with that I can use the radios of the Sparky 747.

I passed on your info on the custom data ref to Pilotedge, hopefully they can do something with it.

Best, J

Hi J
I'm in holliday for skiing, I will see next week. Actually PSX send radiocom to Xplane. If Xplane send to PSX, would it be ok, too?

[JJK]

Hi Thierry,

Enjoy the holidays!

Did some test flying online this weekend with PSX on the Pilotedge (PE) network and Vatsim in the USA using the custom data ref you created. Very nice, smooth bridge now!

Here are my findings of the online flying:

1) the custom speed data ref works on PE, but is sending the speed in km per hour is my guess, as I was doing values between 900 and a 1000 km on the screen of the controllers. Not sure yet for VATSIM how to get the speed send through.
2) On the PSX bridge screen visible in X-plane the GS indicator value you display is actually showing the TAS, not the GS of PSX, here the value is visible in knots correctly.
3) Would it be possible to also send at least 2 transponder modes through with a data ref? Off and Alt mode, as controllers will otherwise not see the altitude.
5) The Altitude is displaying correctly according to the radar controller so I did not use that custom data ref.

Regarding the bridge in general:
Altitude synchronisation for landing still needs some more tuning. (tested KLAX and KSEA several runways).
- The visual model in Xplane puts you a least some 100-150 feet too low on final approach, versus the PSX plane radar altitude.
- The result is that when PSX flies auto land, or if you fly on PSX instruments down to minimums, the X-plane model is too low and will hit the ground before the runway.
- And when transitioning to X-plane visuals and fly the final approach on the PAPIS, you get 1) glideslope deviations alerts (less of a problem), but end up flaring way too early for the PSX plane, with still says it is at 200 feet or so, but you see in Xplane you are actually about to touch down. The result is that PSX lands long every time, touching down past mid runway at best or further.

The altitude slider on the bridge can maybe help out here, but it only has 5 mtrs up and down, not sure if it will do the trick, but the adjustment range could maybe increased up to 50 mtrs up and down? Maybe is there another solutions to this problem?

Regarding your suggestion to use Saitek panels to drive the PSX radios (and multi panel) through Xplane, that would be a really nice thing to have. Look forward to that solution!

Anyway thanks for all the work and happy to go test flying again.

Best, J

[TCASSE]

Hi Hardy,
...I suppose it is not possible to fix the elevation issue between Xplane and psx. Do you have an idee to to get around the problem?
How to get the mode demand (in order to have the groundspeed Qi271)

[Hardy Heinlin]

Do you use Qi198?

Qi198="Elev"; Mode=ECON; Min=-9999999; Max=9999999;

Use this to inject X-Plane elevation into PSX, at a rate of about 1 Hz to 5 Hz.

Multiply the value by 100. E.g. for 3129 feet send: Qi198=312900

Once you have injected a Qi198 value, PSX will use this and your following Qi198 injections for its elevation model. When you inject the value -9999999, PSX will use its own elevation database again.

In short words, to make X-Plane the elevation master, send a value higher than this, and keep sending elevation data:

Qi198=-100000


To make PSX the elevation master, send this and then stop sending elevation data:

Qi198=-9999999


Notice that these numbers are negative (the "minus" sign is a bit small here).


Regards,

|-|ardy

[Hardy Heinlin]

Qi271="GroundSpeed"; Mode=DEMAND; Min=0; Max=99999;

To demand Qi271, send this to PSX:

demand=Qi271

Send it only once. Do not repeat the demand. Once demanded, it remains active.

[TCASSE]

Thank you Hardy or your pronpt answer

[TCASSE]

Hi Hardy,
I send "TfcMode=1\n" ok "Qi198=-100000\n" ok mais "demand=Qi271" non ok. Do I run something before sending "demand=Qi271"?

it's  solved. OK now

[Hardy Heinlin]

If you always need to append the "\n", you need to append it to the demand command too: "demand=Qi271\n"

Actually, you need to append it to all commands, including the keywords "exit" etc.