Your image IMG_3408.jpg is saying "Instrument Panel Test"

Therefore, what is your HSI showing when the GTN is on this page (i.e. is the HSI VCDI is half up like indicated) ?

Hi Jean-Luc

I added pictures,  and put annotations down for each one The following is the link (same as before):  https://photos.app.goo.gl/TKwwHVa8FNMGMv1f8

Pictures of the HSI after each step of the initiation, starts with the pictures labeled 12) and goes through 19)  picture 3) and 4) shows what it looks like after I added a single waypoint.

I then did a ILS approach followed by a GPS approach. The ILS is runway 28 right into Oakland 5) shows me approaching the final approach fix, and 6) shows the instruments – the HSI shows me slightly left of course (ignore the fact that I hadn't yet turned the core selector knob), and below the glide slope. The glide slope will come down and intercept me, and switch automatically from altitude hold to glide slope mode - all of the annunciator buttons are showing things correctly, Note the GS pointer is working correctly.

7) now past the faf, as shown on the GTN 750  😎 autopilot and annunciator panel show glide slope mode, HSI shows on course both laterally and vertically – all is perfect, as confirmed by 9)

here's where it gets kind of strange, I now go back to shoot the GPS – LPV approach to the same runway. This time I did get GS pointer, as shown by pictures 10 and 11.  Every time in the past when I didn't get the GS pointer, it was the first approach of the session, so wonder if first flying the ILS, in some way resolves whatever issue, and future GPS approaches work.

I tested that by rebooting the computer, and this time flying a GPS LPV 28 Left into Hayward, as depicted by pictures 20) and 21). Note the problem as displayed on 21) – the autopilot is tracking the glide slope perfectly (as indicated by the GS on the autopilot, and on the annunciator), and the attitude of the airplane, descending right on glide slope. However, there is no glide slope pointer on the HSI – and this is the problem I see.

Thus, I suspect that flying an ILS first resolves the problem.

Thanks for your help

Charlie

This is interesting and might suggest a bug of some sort in XP11.50 in regard to the 'override' datarefs.

One thing you can easily do to cross-check is the following:

Open dataref editor and look for the following specific datarefs and compare their values vs what is expected.

sim/cockpit/radios/gps_vdef_dot
    The deflection from the aircraft to the tuned in glide slope in dots on an ILS gauge – pilot. override_gps

sim/cockpit/radios/gps_has_glideslope
    does the GPS 1 provide vertical guidance? Write with override_gps

sim/operation/override/override_gps
    Override GPS computer

If the RXP GTN is in control, you should have:

override_gps = 1

and depending on the signal:

gps_has_glideslope = 1
gps_vdef_dot = value of the needle deviation.

 

Then you might want to cross check whether other datarefs are synchronizing per the GPS datarefs:

sim/cockpit2/radios/indicators/hsi_flag_glideslope_pilot
    Glide slope flag, pilot side HSI – EFIS style flag that shows when glideslope is expected, but not received

sim/cockpit2/radios/indicators/hsi_flag_glideslope_pilot_mech
    Glide slope flag, copilot side HSI – mechanical instrument flag that shows whenever no glideslope signal is received

 

These are usually the datarefs 3rd party vendors are using for their HSI gauges and these are supposed to be properly set by X-Plane internally.

Hi Jean-Luc:  I will get to that. In the meantime, I went flying in my Bonanza today, with the real GTN 750 and HSI, and I took some more pictures for you to compare. Like I said before, the simulation environment is amazingly real - I was better with the GTN today, because of the work I did in the past few days on the sim. pictures 22 through 25 are the 750 POST, followed by the real HSI.

 

Charlie

Thank you for sharing these!

You're giving me the idea of adding a new setting in the GUI: Protective Plastic Sheet ON/OFF 🙂

 

Given what that radio costs, we decided to keep the plastic on. It's hardly noticeable, except when I took that picture 🙂

Too bad this doesn't work fully.  But, Dataman100, I want to be sure you know that the flight plan does auto-move from the GTN to the G1000, just the waypoint altitudes need to be entered. (They can't be in the flight plan as I recall. )  It isn't too bad if you program keys for the lower right MFD concentric rotary; then you just punch the button for each 100 foot change.  Maybe a key hold-down repeat could be set up.  We need the G1000 MFD for the weather radar anyway. 

 

On 10/18/2020 at 12:26 PM, tset said:

Too bad this doesn't work fully.  But, Dataman100, I want to be sure you know that the flight plan does auto-move from the GTN to the G1000, just the waypoint altitudes need to be entered. (They can't be in the flight plan as I recall. )  It isn't too bad if you program keys for the lower right MFD concentric rotary; then you just punch the button for each 100 foot change.  Maybe a key hold-down repeat could be set up.  We need the G1000 MFD for the weather radar anyway. 

 

I haven't flown the Mustang in a while. I've been trying to get the GTN 750 to work with the Phenom 100 from Carenado, but I see what you're saying. I can create the flight plan in the 750 and it will populate in the Mustang's G1000, except for the waypoint altitudes which need to be entered manually. I can do that. Just another step while setting up the flight plan. I'll try it next time I fly the Mustang. Thanks!

Has anyone gotten the RXP 750 to work completely with the Phenom 100?  I'm able to use it coupled with the AP to fly a course.  The waypoints are not auto-moved to the G1000 though, but the AP does track them, and the don't show up on the MFD map. I've even been able to get the AP to fly an RNAV GPS approach all the way down to MDA, but it's hit and miss. You have to keep toggling the CDI button on the 750 between ILS and GPS until it captures. The plane will suddenly start descending on the GS although there's no GS indicator on the PFD and no indication anywhere you're actually on a GS. I think this is because the native Phenom 100 doesn't support RNAV approaches so there's no code to get it to display a GPS GS indicator in RNAV mode. It does for ILS approaches though. I found a forum post somewhere that described toggling the CDI button like this and I can get it to capture the RNAV GS about 80% of the time. It seems like a timing thing. If you don't toggle the button at the right time, it won't capture. If anyone has any thoughts or experiences with the Phenom 100 and the RXP 750, I'd love to hear them.

My next adventure is to get the 750 to work with the Challenger 300. I've had limited success but I haven't had a lot of time lately to test it thoroughly. I'm still learning the FMC in the Challenger and I'm not 100% confident with it yet, so I'm still trying to figure out how to map the processes to the 750. If anyone also has any experience getting the GTN 750 to work with the Challenger to fly a GPS approach, I'd love to hear that as well.

Thanks to everyone who has given me so much good info!