PSXView with xplane12, introducing extended TCAS and real life traffic

[TCASSE]

Hi Hardy,

How is the radio altimeter calculated? Since I use the Qi198 with X-Plane's altitude, I have strange behavior with the radio altimeter value. The value increases up to 190, then decreases and stops increasing while climbing to 5000 ft...

[Hardy Heinlin]

Hi, the radio altitude is the distance between the aircraft and the highest obstacle under the aircraft. That gray altimeter tape, however, which goes up to 50000 feet, is a barometric instrument; you may climb barometrically from 0 to 5000 feet along rising terrain while your radio altitude may remain constant or even decrease here and there, depending on the distance between aircraft and terrain.

Look at the graph on Instructor > Analysis > Profile. There you can see the terrain profile. When X-Plane is the elevation master, the graph should show the X-Plane terrain profile.

[TCASSE]

I tested above the see. When I don't use Qi198, radioaltimeter is OK.

[Hardy Heinlin]

I'm not familiar with X-Plane. Are you sure your program gets X-Plane's current terrain elevation (and obstacle height) at the current aircraft lat/lon position?

[Gary Oliver]

I'm not familiar with X-Plane. Are you sure your program gets X-Plane's current terrain elevation (and obstacle height) at the current aircraft lat/lon position?

I started on an Xplane injector and found to get the Xplane ground elevation was not possible via the standard UDP stream and required a plugin

[TCASSE]

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

Hi,
I have made some corrections.
1.Com and tranponder code on/off
2.GS is now groundSpeed in kt
3.I don't understand about transpondeur code. So I put on the display the PSX's value (6 digits) depending of the selected mode.
4. I have made some adjustment concerning the altitude and the altitude slider, better behavior but I 'm not sure to correct the the pb of difference of level beetween Xplane and PSX. Could you test a  PSX instruments flight on LFPO/LFPG and LFMN?
See page 1 for the updated file

[JJK]

Bonsoir Thierry,

This is good news. Thanks, will test tomorrow on the airports you requested and later fly online to see the GS feature and Xpdr.

Keep you posted, J

[JJK]

Good morning,

The landing altitudes now align! Did one autoland and a manual visual approach into the same field I took off from LAX and that goes perfect. Really happy with that. Still need more testing and do the flights you asked.

The GS is correct now in the PSX Sync window. However the Groundspeed custom data ref for PilotEdge is not picking up anything. Did you change the dataref?

Thanks for all the work.
J

[TCASSE]

Good morning,

The landing altitudes now align! Did one autoland and a manual visual approach into the same field I took off from LAX and that goes perfect. Really happy with that. Still need more testing and do the flights you asked.

The GS is correct now in the PSX Sync window. However the Groundspeed custom data ref for PilotEdge is not picking up anything. Did you change the dataref?

Thanks for all the work.
J

I forgot to put back the datarefs ( GS/ALT in meters and transponder code with 6 digits). See page 1.

[JJK]

Hi Thierry,

Bon jour!

The GS that appears on the radar of PilotEdge is km/hour and still reporting the TAS (in km/h) can you replace that for the GS in Knots?

Many thanks!
J

[TCASSE]

Hi Thierry,

Bon jour!

The GS that appears on the radar of PilotEdge is km/hour and still reporting the TAS (in km/h) can you replace that for the GS in Knots?

Many thanks!
J

Hi,
I suppose PilotEdge converts KT in km/h because i send value in kt. You can check this by reading the info in the created windows in xplane. I can cheat by multiply the info by 1.852 if you want...

[voipmeister]

I started on an Xplane injector and found to get the Xplane ground elevation was not possible via the standard UDP stream and required a plugin

Gary, is this a recent thing or something from the past?

[JJK]

Hi,
I suppose PilotEdge converts KT in km/h because i send value in kt. You can check this by reading the info in the created windows in xplane. I can cheat by multiply the info by 1.852 if you want...

Hi Thierry,

I don´t think they convert anything, but if you could divide the value for the custom data ref by 1.852 I guess their output will be correct. And also check if by any chance it is actually the GS and not the TAS. Indeed the PSXView window is showing the correct value.

J

[TCASSE]

Hi Thierry,

I don´t think they convert anything, but if you could divide the value for the custom data ref by 1.852 I guess their output will be correct. And also check if by any chance it is actually the GS and not the TAS. Indeed the PSXView window is showing the correct value.

J

Hi J, try this https://1drv.ms/u/c/9078b8581e0fcab6/IQANXYG1uOVhRaietwPq6b6lAYZ6_04vR1ih6knkCfykEJc

[TCASSE]

Hi J, try this   https://1drv.ms/u/c/9078b8581e0fcab6/IQBmeTKaepUgQZ0TGGWxp-QcAYqglJhwrx7GjakjU17Nkgo

the datafef call psx_bridge/gs_PE

[JJK]

Hi Thierry,

Thanks I tried with the psi_bridge/gs_PE and the new win 1.xpl file in the plugin folder but the readout on the radar is now again zero GS.

Is there something I missed?

J

[TCASSE]

Hi Thierry,

Thanks I tried with the psi_bridge/gs_PE and the new win 1.xpl file in the plugin folder but the readout on the radar is now again zero GS.

Is there something I missed?

J

As I said before, I supppose PE is waiting for a value in KT then converts to KM/H. The read value with the psx_bridge/gs_PE is not correct for PE and not displayed (I suppose). I also let the previous one psx_bridge/gs. Take it. 

[JJK]

Thanks.

Just to be sure I did it correctly, I replaced the win 1.xpl file you send and placed it in the PSXview plugin folder, and renamed it to win.xpl

Correct?

J

[TCASSE]

Thanks.

Just to be sure I did it correctly, I replaced the win 1.xpl file you send and placed it in the PSXview plugin folder, and renamed it to win.xpl

Correct? Yes it's correct

J

Try this. I use an INT instead a float for the Ground Speed (15 KT instead 15,56) https://1drv.ms/u/c/9078b8581e0fcab6/IQAmYS4A521ySr8QnmjIEv9uAavodO26g8lzqKRPgspHNFM

[TCASSE]

Hi Hardy,
Is it possible to only inject the heading to PSX. read Qs121 and send back the values with the "new heading"?  or another methode ?. it's for the start a new flight in accordance with xplane.
Second question: How to invoque bang ? for an update of Qi values
Thank