is there a button you press to activate the new route and a nice arrow pointing you to your new location

 

In addition to what Neil suggested with direct to, those airports, vors, waypoints or whatever that you've previously looked at go into your "recent" list, so if you're in the plan page you can add one of them by clicking "add waypoint" and then if you hit the little magnifying glass "find" icon you can quickly pick it from the top of your recent list.

Thanks, Ebs, but no it doesn't.  If someone could define what the FROM side of the FAF is, as opposed to the TO side, it would be a start. And what exactly is 'full-scale deflection'?  Deflection of what?

I'll try to answer both of your questions as clearly as possible.

 

"Full-scale deflection" is referring to the CDI needle on the HSI. When it deflects, it indicates that it is receiving a signal.

 

Both "TO" and "FROM" are relative terms that depend entirely on both direction of travel as well as current position to the fixed reference point, which in your case is the FAF (Final Approach Fix).

 

When flying your flight plan towards the FAF you are on the "TO" side of that fix. Once you fly past the FAF you are now on the "FROM" side. You are no longer flying towards the FAF, you are flying away from the FAF.

 

At this point, even if you executed a 180º turn and fly back towards the FAF, as far as the flight plan is concerned you are still on the "FROM" side!

 

This is why any GPS will place you in the SUSP mode. The  GPS has no idea whatever what to do because you have not told it what to do... ^_^

Alright, what you describe over on the simforums (missed approach 'imaginary line') and here are two separate things (but are somewhat related). I'll try and explain whats going on, so thanks for posting the flight plan info. Makes it easier for me to recreate.

 

I made a picture to illustrate it.

Does this help at all?

 

Ebs, your clear description and pictures have explained everything. What can I say other than thank you? And if ever we meet, the beers are on me!  This thing has bugged me for months. My PPL training in 1980s was before GPS, but I could pull off a reasonable NDB approach in those days!

 

Yes, you did your good deed today, Ebs, you helped an old-timer!

 

 

Currently enroute to HOBOS with RNAV Rwy 24 KROA activated.

I'll try to answer both of your questions as clearly as possible.

 

"Full-scale deflection" is referring to the CDI needle on the HSI. When it deflects, it indicates that it is receiving a signal.

 

Both "TO" and "FROM" are relative terms that depend entirely on both direction of travel as well as current position to the fixed reference point, which in your case is the FAF (Final Approach Fix).

 

When flying your flight plan towards the FAF you are on the "TO" side of that fix. Once you fly past the FAF you are now on the "FROM" side. You are no longer flying towards the FAF, you are flying away from the FAF.

 

At this point, even if you executed a 180º turn and fly back towards the FAF, as far as the flight plan is concerned you are still on the "FROM" side!

 

This is why any GPS will place you in the SUSP mode. The  GPS has no idea whatever what to do because you have not told it what to do... ^_^

 

Thanks, Fr Bill

 

How can there be an OBI deflection when I am using GPS and not HSI/CDI for the approach?  In the example above for KROA I was tuned to the LWB VORDME outbound on VOR2 and tracking a radial as backup - the weather was mucky, MSA 5700ft . I was attempting to use a RNAV approach to KROA.

 

I just about get the TO/FROM thing now but intuitive it is not. :mellow: In the example above, before I activated the RNAV approach I was flying Towards the FAF, not directly TO it, but not FROM it either.  I accept that I was on the runway side of the FAF, and perhaps this is where I have been going wrong.

 

Is it standard for a GPS, when it enters SUSP mode, to take contol of the aircraft and make a 90 degree turn?  I would have thought that when the instrument went into SUSPEND that the aircraft would continue on its current course,  i.e. 'resume own navigation'. That is not what happened in this example and other times when I had the same difficulty. I am fussy about the heading bug - it was exactly where it should be - straight ahead.

I'll try to answer both of your questions as clearly as possible.

At this point, even if you executed a 180º turn and fly back towards the FAF, as far as the flight plan is concerned you are still on the "FROM" side!

 

Exactly. BUT... for what I have seen, this only happens as long as you're trying to activate the loaded approach from a position that the GPS considers as past the FAF and therefore on the "FROM" side. However, you can fly back to the IF, FAF or any other waypoint of the approach with a direct leg and then activate the approach. Tried and tried many times, it works. Now, probably this is not what is supposed to happen in real life, but as far as the issue mentioned by betelgeuse is concerned, the solution is always to fly back to the IF, FAF or any other waypoint with a direct leg (or even in manual, why not) and then to activate the approach.

 

Currently enroute to HOBOS with RNAV Rwy 24 KROA activated.

 

Assuming your starting point is the same as described in your first post, that is 10nm NW from LWB VOR, there is no need for you to fly until HOBOS to activate the RNAV (GPS) RWY 24 approach. Unless you really want to. You can fly a direct leg to HIBAN (FAF, 3700 ft) or to PROSE (IF, 4700 ft) and then activate the approach. I tried to reproduce your situation and opted for flying directly to PROSE. When in the vicinity of PROSE, with the RNAV (GPS) RWY 24 loaded but not active, the GTN automatically activated the sequencing until RW 24 and the aircraft turned 251° headed to HIBAN. At this point I could finally click "ACTIVATE VECTORS TO FINAL" and follow the approach until RW 24. Again, I don't know if this procedure is correct and is supposed to happen in real life, but it works when you are in the situation you described.

Assuming your starting point is the same as described in your first post, that is 10nm NW from LWB VOR, there is no need for you to fly until HOBOS to activate the RNAV (GPS) RWY 24 approach. Unless you really want to. You can fly a direct leg to HIBAN (FAF, 3700 ft) or to PROSE (IF, 4700 ft) and then activate the approach. I tried to reproduce your situation and opted for flying directly to PROSE. When in the vicinity of PROSE, with the RNAV (GPS) RWY 24 loaded but not active, the GTN automatically activated the sequencing until RW 24 and the aircraft turned 251° headed to HIBAN. At this point I could finally click "ACTIVATE VECTORS TO FINAL" and follow the approach until RW 24. Again, I don't know if this procedure is correct and is supposed to happen in real life, but it works when you are in the situation you described.

 

Yes, I get that now. 

 

In fact I was able to activate the RNAV Rwy 24 approach to KROA from 10nm NW LWB using HOBOS as transition. No dreaded SUSP notice B)  From that it would seem that I could have chosen CARUS as the transition even from that starting position, and this would have been good too.

 

In summary, my understanding is that SUSP is likely if VECTORS are selected and the plane is on the WRONG side of the FAF i.e. on the runway side when the initial activation request is made. Otherwise, ignore SUSP and fly manually or DCT to a transition. At that point UNSUSP should activate the approach. If this is wrong, please correct me. 

 

Finally, finally, thanks to all who helped on this thread, especially Ebs who made all the lovely pics.  :smile: :smile:

Ebs thanks for the great flight setup you provided. I did manage to make it work although I am sure I did several things wrong. First after setting it up I did not get a magenta line to the final destination but did get a dotted line instead that the gps did follow right to the correct runway. I also set up and activated my approach way too early but it still worked.

 

Next I would like to know how to add decent altitudes to the final approach. 

 

 

Ebs, your clear description and pictures have explained everything. What can I say other than thank you?

 

You're more than welcome John, any time. I could sense a bit of frustration in your posts, but at least you kept it civil!

All I ask is that you 'pay it forward'. If you see a user on a forum struggling a bit with an addon and you can help, give a bit of your time and help them out. We've all been there!

 

Glad it's sorted out for you,

Neil.

 

 

In addition to what Neil suggested

 

 

Yes Elaine, while you're looking at the airport info, click the physical DIRECT TO button on the right hand side of the GTN (D with an arrow going through it), then the Activate

 

Great stuff, Thank you Neil and Jim,   its an amazing app 

 

 

All I ask is that you 'pay it forward'. If you see a user on a forum struggling a bit with an addon and you can help, give a bit of your time and help them out. We've all been there!

 

Oh but has Neil stated a core principle that has caused this site to be so successful and meaningful.

Is there anyway to brighten the screen of the GTN 750? In the Duke the screen is darker than the guages and sometimes harder to see. I know it is not possible within the units system utilities but maybe in the panel config?

Is there anyway to brighten the screen of the GTN 750? In the Duke the screen is darker than the guages and sometimes harder to see. I know it is not possible within the units system utilities but maybe in the panel config?

There is a setting in the gtn750 config file for brightness, Check to see if it's set to 100%.

The config file is in the duke airplane folder, make sure there is an entry in all sections ( GTN 750. 1 )

 

bob

 

P's ... VC Brightness=100

There is a setting in the gtn750 config file for brightness, Check to see if it's set to 100%.

The config file is in the duke airplane folder, make sure there is an entry in all sections ( GTN 750. 1 )

 

bob

 

P's ... VC Brightness=100

 

 

You can do that from within the F1GTN config tool, no need to edit CFG files.  

 

Just go to "Configure GTN" then select the unit from the top bar then scroll right down to the bottom.

You can do that from within the F1GTN config tool, no need to edit CFG files.

 

Just go to "Configure GTN" then select the unit from the top bar then scroll right down to the bottom.

thanks Jamie, that's been pointed out to me before, with your explanation found it ok, yes a much better way.

thanks bob

That fixed it for daylight but -

 

I found the setting and set it to 100. Now it works ok and is much brighter in daylight but at dusk, dawn and night it reverts back to dimmer than gauges.