RNAV LVARs
-
I am trying to get the information displayed on the KNS81 using the LVARs listed in the manual, but the values do not match the displayed numbers shown in the instrument. Are they the correct LVARs to be used for such purpose?
L:var_RNAV_WAYPOINT_NUMBER => it's not available thru spad.next
L:var_RNAV_RADIAL_NUMBER shows 0 (but the display shows 360)
L:var_RNAV_DME shows 0 (but the display shows 5.0)
NAV STANDBY FREQUENCY:3 this is the only one which information matches the instrument information displayedmanual
-
@hangar_101 these are the variables that work for me, that show what's on the unit's display:
(L:var_RNAV_WAYPOINT_NUMBER, Number)
(A:NAV STANDBY FREQUENCY:3, Hz)
(L:var_RNAV_RADIAL_NUMBER, Number)
(L:var_RNAV_DISTANCE_NUMBER, Number)
(L:var_RNAV_DME, Number)
is the distance from your position to the calculated waypoint - what's shown on the DME instrument.cc @Black-Square, there are however a couple of problems with these that I observed:
- the RNAV_RADIAL_NUMBER and RNAV_DISTANCE_NUMBER are zero unless there is actually a correct VOR signal being receiver on the chosen frequency
- when the plane is stationary on the ground, the DME display when switched to RNAV mode, starts counting wildly upwards till it reaches 999.9 and stays there
Here is a screenshot of the DME display readout blurred because of the wild count-up :)
-
@Randolf said in RNAV LVARs:
when the plane is stationary on the ground, the DME display when switched to RNAV mode, starts counting wildly upwards till it reaches 999.9 and stays there
I saw this for the first time today and immediately found the problem. It was due to the interpolation I added to enable autopilot tracking from the RNAV system. Believe it or not, the DME information update interval from the simulator is so slow that it cannot be used to accurately drive an autopilot! I suspect that code has been unchanged since the 1980's.