how to modify AP source switch to add NAV2

[tgibson_new]

Hi,

 

I fixed the link; it works now. The file name is navinstdcbjrv1.zip here at flightsim.com.

[tiger1962]

I don't fully see what you mean by that last sentence "no switch is necessary".

 

My apologies il88p, I didn't explain very well there. Because the NAV Mode option in FS2004 drives NAV1 only, when you switch your gauge from Nav1 to Nav2 you're actually switching NAV Mode off altogether because the FS2004 NAV Mode has no built-in code for a Nav2. The gauge which Tom mentioned might have it's own NAV Mode for a Nav2 or some other workaround built-in, such as the Nav2 switch activating the OBS2 frequency instead for example.

[il88pp]

Thanks both, messages recieved and read. Some sinking in required. Will do a little flight, add some fresh songs to the music playing gauge in the plane. Clear my mind a bit.:)

[il88pp]

I was able to confirm my gauge works.

 

To fly straight to a VOR, along a pedetrmined heading, Using the frequency that is set on nav2:

-select Nav2 on my gauge,

-tune the frequency of the VOR in nav2 radio,

-set OBS2 to the heading you want (lets say 070),

-witch on Autopilot, and select "Nav Hold" and Altitude Hold".

-Even though it's Nav1 hold officially, the plane now flies to the VOR that is tuned on nav2 radio, along heading 070.

 

If you are not on the 'line' that goes to the VOR along that heading, the plane will turn to intercept that line, and then follow it after intersecting.

 

---------

To test I installed all the gauges from the file Tom Gibson linked (filename: navinstdcbjrv1.zip ), on a popup panel, and placed my gauge on there as well.

That gave me two switches to select nav1/nav2/gps. My own one, and the one from the file.

Also an OBS1 and OBS2

And three I did not need, for gyro calibration.

One more needed to be installed, gauge: NavSelectDD.gau (Which I thought was required, but I wasn't sure)

 

I quickly saw clicking my Nav1/nav2/gps guage moved the other nav1/nav2/gps guage as well. That told me my gauge fires the correct commands.

 

After some tries I managed to fly the plane to VOR using the frequency on Nav2.

 

I then tested if the presence of the other nav selector switch was required.

I also tested if the presence of the NavSelectDD.gau gauge was required.

Both were NOT required.

 

----------------

It seems I had just not found the correct autopilot settings to make it work.

The reason for that; I had not tried it in a plane that has an OBS2 gauge dial.

 

A final test I installed only my gauge in the Cessna172. That plane does have an OBS2

No files from (filename: navinstdcbjrv1.zip )

In the same autopilot setup as before, (my gauge to NAV2, VOR tuned on nav2, OBS-2 set to the heading, AP-Alt-Hld ON, AP-Nav-Hld ON) the plane flies to the VOR along the heading I selected.

 

So my gauge does the trick. Nothing else needed. All that is required is the plane must have OBS-2

 

------------------------

I decided to test the functioning of the gauge in the downloaded files.

I installed only that nav1/nav2/gps switch.

I couldn't switch it to nav2. It didn't respond when clicked.

 

Then I installed the other (possibly required) gauge from that package: NavSelectDD.gau

After that I could use the nav1/nav2/gps switch to NAV2.

 

So, it seems that for the functioning of the switch in that package, the .gau file is indeed required.

 

But for my gauge functioning it is not required. You just need an OBS-2

 

----------

 

Thank you Tom and tiger1962.

All sorted out.

 

PS.

More to discover. May look into a way to make my gauge move with together with the default NAV/GPS-MODE switch. Now when the default switch is used my gauge does follow this action. It keeps showing the old setting.

 

another thing I'll look at is, the nav1-2-gps switch from the package does not go to NAV2 when clicked if NavSelectDD.gau isn't active too.

But if both my nav1-nav2-gps and the one from the package are installed, then, clicking my switch to nav2, sets the one from the package to nav2 as well.

That means the nav1-2-gps switch from the package shows it's images by listening to some SIMvariable that my gauge sets.

If I can make my gauge listen to that same SIMvariable and show my images accordingly, then that should fix the issue with my gauge not following the default NAV/GPS-mode switch.

[il88pp]

I should have said sooner. I use FSX.

So I was only able to test this gauge in FSX.

 

I did keep in mind that this is the FS2004 forum, so I used FS2004 gauge syntax and Variables. So I think the gauge will work in FS2004 as well.

But I can't guarantee that.

 

If you don't get it to work right away, don't give up too easily.

I had to first select heading hold, and then Nav hold on the autopilot, to get it to fly to the VOR.

Other times turning the OBS dial afte nav hold was engaged got things going.

Sometimes nav hold switches off, and you need to switch it on again.

[ngtw16a]

Confirmed it works....with a but.

 

I tested on FS2004 using the stock c172...

 

IF you switch from nav1 to nav2 (source)...then click AP_NAV....nothing...

it tracks to nav1

 

IF you switch the AP_NAV on FIRST--then quickly switch source to nav2...it DOES

track...

 

so it appears the AP_NAV button...must reset the source back to NAV1...

 

I didnt try using vor2 for an ILS approach...without the glideslope needle I didnt see the point.

 

I didnt try the heading hold first as above...will try that next!

 

My exact example...

I flew To VOR1 on radial 90, after passing it....I turned the AP_NAV on again (went off as I overflew), then selected NAV2....and it tracked using OBS2 on radial 105..away..

 

I then changed nav1 freq to ils approach...and when at IP...clicked back to nav1

and it turned onto the ILS...THEN I could click AP_APPR and let the approach do its thing.

 

So I guess as long as think about it carefully--it works (at least for what I need).

 

Many thanks to all.

[il88pp]

I did some testing from an airport EHRD (Roterdam), flying towards EHAM (Amsterdam Schiphol)

I took off from RW06 EHRD.

From there VOR AMS (108.40) is at around 30 degrees bearing.

I tuned vor AMS

and had OBS-2 set to heading 000

 

I took off, and set a climb on autopilot. No horizontal navigation yet.

 

I selected nav2-source with my gauge. Then engaged nav-hold on autopilot.

The plane did not respond.

Then I turned the OBS-2 dial so the needle centered. So I dialed the OBS dial to 030.

At that moment the plane started following the OBS-2 and Nav2.

 

I then turned the OBS-2 back to 003

The plane now banked right, to intercept the radial leading to the VOR at heading 003. All working as planned.

 

I find that very workable. You tend to rotate the OBS dial towards the vor anyway.

 

------------

I also tested your finding, but couldn't confirm.

I think what happened is you were for some other reason banking to the side that made you have the VOR straight in front of you. Or maybe you just happened to rotate the OBS-2 dial a bit.

 

In a second test I took off wings level. I engaged AP altitude hold for a steady climb to 3000.

I engaged nav-hold, I then clicked the Nav2-source selector. Tried clicking it some more. But the plane kept climbing/flying straight on.

However, as soon as I rotated the OBS-2 dial, things started working as planned.

 

climbing - obs2 at 000 - VOR is at 030

 

 

nav-source2 and nav -hold engaged

Nothing happens yet.

 

 

Then I rotated OBS-2 to direction VOR is in. About bearing 030.

Now it takes

 

 

Rotated OBS-2 back now, to heading 003 again.

Plane turns right to intercept that course to VOR.

Great, because if you approach EHAM at that heading, you are lined up for 36L 36R and 36C.

 

 

 

Result, flying to VOR, along heading selected earlier on OBS-2

 

 

 

 

 

So dialing the OBS-2 to the vor heading sets thing n motion.

And clicking nav-hold on does not reset the source.

(At least in FSX)

 

One note. If you are fling to VOR. As soon as you overfly the VOR, Navhold switches off!!

[il88pp]

I just found out you can also use this methofd to make the plane fly FROM the VOR.

By setting a heading away from it on OBS-2.

 

 

Like so:

Here VOR-2 (110.40) is directly behind me. The plane follows OBS-2, and heads away from VOR at heading 120.

The VOR is directly behind me. At bearing 300.

 

To have this engage, I again had to rotate the OBS-2 dial.

I had to rotate the dial to center the needle, but this time with the "FROM" indicator showing.

 

[il88pp]

I noticed from time to time the heading it flies is not the same as the VOR is in, but that's not due to the gauge.

It has to do with gyro-precession.

If I reset the gyro (d key in fsx) it is ok again.

 

(the package Tom Gibson linked had three gyro gauges as well. (With adjustable dials, to calibrate the gyro.))

[il88pp]

I just did a flight with landing.

 

I flew the Cessna172

I was west of EDDF (Frankfurt Germany)

I flew to VOR FFM (Frankfurt Main) along heading of 069.

With OBS-2 set to 069, radio nav2 tuned to FFM (114.20), My gauge to nav2-source, and AP nav-hold on.

 

I flew at an altitude of 2000 ft, and was about 20NM from the VOR. (distance seen on the radio panel.)

 

I had tuned nav1 radio to RW07C (I use an addon for EDDF that has three runways 07. L, C, and R, instead of the default two runways.)

 

The VOR FFM is about 3 NM east of the airport. So when distance to VOR was 20NM, I was 17 NM from the airport.

At that point I saw the OBS-1 indicator come to life. It indicated I was pretty much lined up. And below the glideslope.

 

I used my gauge to switch Source to nav1

Then selected Apr-hold on the autopilot.

The plane did the last bit of lining up with the localiser, and the glideslope started to come down.

When intercepting the glideslope, the plane started to descend along the glideslope.

 

I slowed the plane a little, set flaps, and landed perfectly.

 

In summary, I used nav-2 to make AP fly to airport along RW heading. To VOR near airport.

I used nav-1 to land with Apr-mode following the ILS as normal.

 

 

**nav2-source. Flying TO FFM along 069 degrees.

(RW freq already tuned on nav1-radio and ready to go)

 

 

**Switched source.

Nav-1 source and app-hold selected

Plane folows ILS.

 

 

---------------------

I like that method a lot.

I thought that was actually what you were trying to achieve when I first read your original post.

 

As to what you said in your last post. No idea if you can make the plane follow a glideslope if you tune the ILS on nav2.

I would need to do another testflight.

The package Tom Gibson linked did have an OBS-2 dial included. I'm not 100% sure, but I think that had a glideslope indicator in it.

I'll check.

 

-------------

Tried it.

Yes, the gauges in that package do includee a OBS2 with a glideslope indicator.

and

Yes, if you tune the Runway frequency on nav2 radio, and have my gauge set to

nav2-source, then...

apr-mode on the autopilot guides the plane in, and makes it follow the glideslope as well!

To be sure it was really nav2 radio that guided, I tuned nav1 radio to an empty frequency.

 

 

**TO vor FFM 114.20. Along heading 069 again jus like above, so perfect for RW07-C at EDDF.

On nav-hold on AP.

 

 

Switched ILS freq on nav2-radio from standby to active.

Kept source set to nav2-source.

Engaged approac mode. Plane folows glideslope

**Almost down, glideslope and localiser are centered. (see OBS -2 in popup)

 

 

 

 

 

 

The OBS-2 indicator with glideslope, from the package, is not required to make it follow the glideslope. It is a useful gauge to observe what is going on.

---------------

I'll post the poup I'm using. As in the package Tom linked, there are only instructions for installing that nav1-nav2-gps switch and the

 

required gauge that's required for it to work. No instructions for the other gauges.

This is just a very basic popup. Doesn't look good, but show you want gauges can be added. (they are in the .cab file).

 

[Window Titles]

WindowXX=nav-1-2-gps and extra

 

[WindowXX]

Background_color=16,16,16

size_mm=380,90 //150,250 //Use if using all gauges

//size_mm=90,90 //Use If using only gauge00=ngtw16a_gau

position=8

visible=0

ident=nav1_2_gps_and_extra

 

gauge00=ngtw16a_gau!ngtw16a_gau, 0,0,80,80 //150,250

//gauge02=NavInstDCBJRv1!APNavSelect, 80,1,50,50

gauge03=NavInstDCBJRv1!ADF1_lrg, 130,1,50,50

gauge04=NavInstDCBJRv1!ADF2_lrg, 180,1,50,50

gauge05=NavInstDCBJRv1!GYRO, 230,1,50,50

gauge06=NavInstDCBJRv1!Vor1_lrg, 280,1,50,50

gauge07=NavInstDCBJRv1!Vor2_lrg, 330,1,50,50

//gauge08=NavSelectDD!NavSelect, 5,5,5,5 //REQUIRED FOR gauge02=NavInstDCBJRv1

[tgibson_new]

Glad to hear it's working.

 

The last thing you might want to do is get rid of the G:Var1 variable and instead test for the position of the NAV1/NAV1/GPS settings in FS to display your knob position. That way if an external source changes that setting (i.e. another gauge), your knob will move along with it.

[tiger1962]

That's good advice, G:Var's are likely to 'forget' their values when you close their gauge pop-ups or change panel views. It's safer to use L: variables instead.

[il88pp]

I was already thinking along those lines, but thanks for reminding.

What I have so far has become a bit messy. Many slightly different versions. I need to consolidate what I have first.

During those last tests I used the gauge as posted at the start. Just to be sure.

 

I was not worried so much about forgetting G: Vars. Hadn't heard about that.

I was more worried about the gauge button not responding to other ways of firing the same command. Such as using a shortcut key.

I think the gauges Tom linked can give me a clue on what variables to use. i'll try to make my images respond to those Variables.

But, as I said, consolidate first. Then work on it some more.

(Plus, to be honest, I like this so much I can't get enough of doing approaches in the Cessna172!! :cool:)

 

Thanks for all the help so far, and ngtw16a, thanks for this idea. having fun!

 

il88pp.

[il88pp]

I managed to make it work.

 

Now the gauge shows the selected position as soon as it appears.

It now listens to the sim's (A:Variables) to show the images.

 

To make sure the gauges don't get Mixed up, I made this new version as a separate new one.

New filename, folder name, new images, and different image names as well.

 

I will repost the whole gauge and include install instructions, images, etc.

See next post.

[il88pp]

Making the gauge and install instructions.

For gauge to select nav1-nav2-and gps as autopilot source.

gaugename: nav1_nav2_gps_sw_il.xml

 

To be able to use nav2 for navigation, you will need a OBS-2 selection dial in

the aircraft as well.

I will add some instructions for using in a later post in this thread.

--------------------------------------------------------

--------------------------------------------------------

 

Create an empty folder on desktop.

Name the folder: nav1_nav2_gps_sw_il

 

-----------------------------------------------

 

Download the following 4 Images and put in that folder.

Four Images.

Are Jpeg files when posted on flightsim.com.

You must Convert these files to .bmp using an image editor.

Size should be 170x88 pixels

Filenames should be ok after download. I put the filenames above the Images just in case.

 

 

nav1_nav2_gps_sw_il_background.bmp

 

nav1_nav2_gps_sw_il_GPS.bmp

 

nav1_nav2_gps_sw_il_NAV1.bmp

 

nav1_nav2_gps_sw_il_NAV2.bmp

--------------------------------------------------

 

Create a .txt textfile.

Name it: nav1_nav2_gps_sw_il.txt

Open the file with Notepad. (don't use other editors).

Put following code in textfile:

 

(A:AUTOPILOT NAV SELECTED,number) 2 * (A:GPS DRIVES NAV1,bool) +


















 (A:GPS DRIVES NAV1,bool)
      if{ 1 (>K:AP_NAV_SELECT_SET) c 0 (>K:TOGGLE_GPS_DRIVES_NAV1) }
      els{ 1 (>K:AP_NAV_SELECT_SET) } 
nav1




 (A:GPS DRIVES NAV1,bool)
      if{ 2 (>K:AP_NAV_SELECT_SET) c 0 (>K:TOGGLE_GPS_DRIVES_NAV1) }
      els{ 2 (>K:AP_NAV_SELECT_SET) } 
Nav2




 (A:GPS DRIVES NAV1,bool)
       if{ 3 (>G:Var1) }
        els{ 1 (>K:TOGGLE_GPS_DRIVES_NAV1,toggle) } 
GPS

 

 

 

Put textfile: nav1_nav2_gps_sw_il.txt

in folder: nav1_nav2_gps_sw_il

Then to make textfile into working gauge, change file extension from:

nav1_nav2_gps_sw_il.txt

to

nav1_nav2_gps_sw_il.xml

 

--------------------------------------------------

 

 

Place folder: nav1_nav2_gps_sw_il

In the panel folder of your aircraft.

Or, if you want to use it with more then one plane, place the folder in

the Main /Gauges folder

 

-----------------------------

Install procedure:

----------------------------

Simple install as popup in the panel.cfg file:

 

[Window Titles] section

windowXX=nav1-nav2-GPS select

 

[WindowXX]
Background_color=16,16,16 
size_mm=50,50
position=8
visible=0
windowsize_ratio=1.0
zorder=10
ident=nav_gps_select

gauge00=nav1_nav2_gps_sw_il!nav1_nav2_gps_sw_il,     0,0,50,50

 

Change XX in that to the next consecutive popup number in your panel.

Use the same number for XX in both added setions.

 

 

The edge of this gauge has no clickspot area. You can use the edge of the gauge to drag the popup

around and to resize it.

The popup panel is the same size as the gauge.

 

---------------------------------------------------

Adding to an existing popup Window, for example

adding to the Main 2D panel:

In the [Window00] section add:

gaugeXX=nav1_nav2_gps_sw_il!nav1_nav2_gps_sw_il,   H, V, w, h

in that line you need to edit the values to:

H=horizontal position,

V=vertical position,

w=width of gauge

h=height of gauge

 

(Add below the last gauge on the popup panel, and change gaugeXX= to the next consecutive number.)

(So if last gauge was guage=55, then add this as gauge=56)

 

 

In my Cessna172 in FSX I have it on the main panel as:

gaugeXX=nav1_nav2_gps_sw_il!nav1_nav2_gps_sw_il, 264,350,26,26

I can't give the position coordinates to install in FS2004 aircraft. I only have FSX.

As you can see the size I chose is 26,26

 

-----------------------------------

The gauge has three clickspots. To select a setting, click in that area.

It is not an "increase/decrsease" selection with + and - sign appearing.

 

 

=Licence agreement:

=You are welcome to use this gauge on your pc and make as many copies of it

=on that pc as you want.

=Also on your other pc's if you have those.

=

=You do not have permission to share this gauge in any form.

=This does not apply to Flightsim.com Staff.

=As I posted this gauge in the Flightsim.com forum, it is their decision on

=which pages of their Forum it is shown.

=

=You are of course free, even encouraged to learn from the code. And then to

=use the inspiration you get to help you in your own creations.

=By all means, go out and create as many of your own gauges as you can!!

=

=I can not give guarantee on functionality of the gauge.

=Use at your own risk!!

=il88pp

=End licence agreement.

 

 

Enjoy!

il88pp.

[il88pp]

Gauge to select nav1 - nav2 or gps as autopilot source..

With the default nav/gps switch you can only select between nav1 and gps.

 

Instructions for use:

 

Tune a VOR within reach to nav2-radio.

On my gauge select nav2 position.

switch on the autopilot nav mode.

turn the OBS-2 scale, so it is allgined straight to the VOR, or, straight away from it.

 

at that moment the autoiplot navigation takes control.

The plane starts to turn to the VOR. Along the heading you put in the OBS-2 scale.

That means it will fly straight to it.

The plane will overfly the VOR at the heading in OBS-2.

 

 

When the autopilot has taken efect, you can also turn the OBS-2 scale to a different heading.

If you do that, the plane will still overfly the plane at the heading you set.

 

If you set the OBS-2 bearing straight aeay from the VOR, the autopilot will also engage.

The plane will then flt away from the VOR.

 

 

Be aware that if the autopilot is followingnav-2 navigation,

-when you switch the nav2 radio frequency, nav hold will switch off.

-when overflying the vor, nav hold will switch off.

-when you use my gauge to switch the source to nav1, nav hold will switch off.

 

With my switch in the nav2 position you can also use nav2 as ILS guidance.

Approach as usual, and select aproach mode on the autopilot.

To follow your landing, you will want an OBS-2 with a glideslope indication.

 

Gyroscopic precession will affect the navigation. Regularly rest the gyro.

 

------------

An example with an image:

Lets say you are south-east of the VOR you want to fly to.

the VOR is at bearing 300

the VOR is tuned on nav2 radio,

you select nav2 source on my gauge,

you select nav-hold on the autopilot,

you turn OBS-2 to 300. (straight to the VOR).

 

The autopilot takes effect, and uses the nav2 frequency, to fly to the VOR.

If you do nothing, the plane will fly staight to the VOR, and reach it flying at a heading of 300.

 

If, when the autopilot has taken control, you re-adjust the OBS-2 scale to 270.

The plane will fly north for a while, and it will then turn left towards the VOR.

That way it will eventually approach the VOR at heading at heading 270.

 

Image:

path1 - Blue - OBS2 set to 300

path2 - Green - OBS2 set to 300, then adjusted to 270

path3 - Red - OBS2 to 300 for a while, later adjusted to 270.

 

[il88pp]

On this image you can see the popup panel and the gauge as it looks on a the main panel.

 

When installed on a panel with a background image you don't get the black corners that you see in this popup.

 

[il88pp]

I suggest to stop using the gauge I posted earlier in the thread, and to use the new one instead.

 

Having them both installed at once will not cause any errors.

But the first gauge doesn't work a 100%. That switch does not move in sync when other nav/gps switches are clicked.

This new one does move in sync.

[il88pp]

Has anyone tried this new version out yet?

If you have, did it work as expected? (please also mention your version of FS.)

 

And was the install problem-free?

 

Thank you,

il88pp.:)

[PhantomTweak]

I am sorry, I haven't had a chance to give it a good test out yet. I got busy with the Race, and working on testing out the latest FSDT F-18, but I still plane on getting it installed annd tested asap, I promise :D

Pat☺