Jump to content
Sign in to follow this  
SchneiH2

Generic instruments, problem with NAV1 indicator

Recommended Posts

Hi everybody

I came across another issue with generic instrumens/datarefs which seems to me very strange. I have added to the standard HSI on the PFD 4 generic needles for NAV1, NAV2, ADF1 and ADF2. As dataref for the NAV’s I use sim/cockpit2/radios/indicators/nav1­ (2)_bearing_deg_ mag. However, the indication in XPlane is obviously ‘wrong’, i.e. if I take the indication from the standard EFIS (which is indeed correct) as benchmark the generic needles show some strange heading bug. To my understanding the configuration of the generic needles in PlaneMaker is correct. Frankly speaking I have no clue what might be wrong  

Thank you very much up-front and best regards

SHJ

2016-02-29_181902.png

2016-02-29_182114.png

Share this post


Link to post
Share on other sites

Hi Jim
Thank you for your response. Unfortunately, this does not work either. However, I think I came a bit closer to the problem. The indication of the bearing itself is obviously correct (absolute value. see also attached pic). Means to absolute coordinates with 0 degrees at 12 o'clock. The 'wrong' thing is that it is not in relation to the current indication of the HSI rose. There is no difference in the behaviour if I use sim/cockpit2/radios/indicators/nav1_relative_bearing_deg or sim/cockpit2/radios/indicators/nav1_bearing_deg.2016-03-02_182215.thumb.png.1b1111c7dacb2016-03-02_183054.png.0cf2d31b9b4b2af3f7

Perhaps you could look again into this matter and give some idea.

Thank you and best regards

SHJ

Share this post


Link to post
Share on other sites
2 hours ago, SchneiH2 said:

The indication of the bearing itself is obviously correct (absolute value. see also attached pic). Means to absolute coordinates with 0 degrees at 12 o'clock. The 'wrong' thing is that it is not in relation to the current indication of the HSI rose.

I suggested the use of the DataRef with "relative" because it is "in relation to the current heading" or HSI compass rose.  You second screenshot shows the pointer at 90 degrees, which I believes is the default position when there is no signal to the radio.  Make sure you have a NavAid tuned in that is in range.

Share this post


Link to post
Share on other sites

Hi Jim
Thank you very much for your reply. In fact this also my understanding of 'relative bearing'. The second screenshot shows a situation where the NAV1 IS tuned to the ILS (please refer to the HSI on PFD) and on the MFD rose the NAV1 pointer shows the correct direction (same direction as ILS indicator, screenshot was made when plane is positioned on that runway). This is exactly the point where I got stuck, i.e. that on the MFD the NAV1 pointer indication is absolutely correct.

Do you have any idea in which direction I should investigate this matter further?
Thank you nad best regards
SHJ

Share this post


Link to post
Share on other sites

Is the MFD built with generic instruments?, or is that a default instrument?  In any event, I would really need to have the aircraft to diagnose the situation.  However, I still believe that the "sim/cockpit2/radios/indicators/nav1_relative_bearing_deg" is the correct one.  

Share this post


Link to post
Share on other sites

Hi Jim
Thanks for the quick response. Yes, the MFD is the default instrument. That's why I am so puzzled. I will countercheck again all setup of the generic instrument (NAV1 indicator) etc. and let you know.
Thank you again and best regards
SHJ

Share this post


Link to post
Share on other sites

Hi Jim
A short feedback on some progress: Except NAV1 (ILS) everything now works fine. I could not find a basic mistake, however, what I did is to build the indicators again from scratch in the 2D-panel of PlaneMaker. After having tested the 2D-panel  I copied them to the 3D-panel where everything seems to work fine. To my surprise this approach (building from scratch) did not work if I did it directly in the 3D-panel of PlaneMaker. The situation with the NAV1 remains strange. If I tune NAV1 to a VOR it works fine but as soon if I tune it to an ILS frequency it does not work (although there is a correct indication in the default EFIS means there is a signal). Is there perhaps some setting missing in my setup of XPlane10? By the way, i have tested it with a 'standard' plane of XPlane10 (B747 NASA) with the same result.

Best regards

SHJ

Share this post


Link to post
Share on other sites
2 hours ago, SchneiH2 said:

If I tune NAV1 to a VOR it works fine but as soon if I tune it to an ILS frequency it does not work (although there is a correct indication in the default EFIS means there is a signal).

Ahhh... so that clears things up a bit. (ILS is not omnidirectional).  

Try using this....

sim/cockpit2/radios/indicators/nav1_relative_heading_AHARS_deg_pilot

  • Upvote 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×