Garmin GNS 400W, Pilot'S Manual & Reference

Page: 195 / 220

11 - MESSAGES
ABBREVIATIONS &
NAV TERMS
185 190-00356-00 Rev G
No altitude input is being received — No altitude data
is being received from RS-232 (Serializer: Icarus, Rosetta or
Shadin) or grey code inputs. If the problem persists, contact
your Garmin dealer and check the installation and installa-
tion settings.
No basemap data available — The 400W-series unit
has detected a failure in the built-in basemap (land data)
memory. Land data does not appear on the Map Page.
Other unit functions continue to work normally, however
the 400W-series unit should be taken to your Garmin
dealer for service at your earliest convenience.
NON WGS84 WPT — Do not use GPS for nav to
[xxxxx].
The position of the selected waypoint [xxxxx] is
not calculated based on the WGS84 map reference datum
and may be positioned in error as displayed. Do not use
GPS to navigate to the selected non-WGS84 waypoint.
Non-WGS84 wpt navigation [xxxxx]. — The position
of the selected waypoint [xxxxx] is not calculated based on
the WGS84 map reference datum and may be positioned
in error as displayed. Do not use GPS to navigate to the
selected non-WGS84 waypoint.
Not receiving input data on 429 Channel #1 or #2 —
No data has been received on the ARINC 429 channel con-
nection for a period exceeding five seconds. If the problem
persists, the installation should be checked by your Garmin
dealer.
Not receiving input data on 232 Channel #(1 through
4) —
No data has been received on one (or more) of the
RS-232 channel connections for a period exceeding ten
seconds. If the problem persists, the installation should be
checked by your Garmin dealer.
Not receiving traffic data — No traffic data is being
received. If the problem persists, the installation should be
checked by your Garmin dealer.
NRST key stuck – The NRST key is stuck in the enabled
(or “pressed”) state. Try pressing the NRST key again to
cycle its operation. If the message persists, contact your
Garmin dealer for assistance.
OBS key stuck —
The
OBS
key is stuck in the enabled
(or pressed) state. Try pressing the OBS key again to cycle
its operation. Check for proper operation of both the inter-
nal and remote keys (if present). If the message persists,
contact your Garmin dealer for assistance.
OBS not available —
The
OBS
mode could not be
activated, because 1) no destination waypoint has been
selected, or 2) the GPS receiver cannot currently determine
its position.
Obstacle database integrity error — The 400W-series
unit has detected a problem with a database on the
HTAWS/Terrain data card. The data is not usable and the
card should be returned to your Garmin dealer for service.
Position outside terrain database coverage region
–This is supplemental information to explain why “TER
N/A” is being annunciated.
RAIM position warning — Although sufficient GPS
satellite coverage may exist, Receiver Autonomous Integrity
Monitoring (RAIM) has determined the information from
one or more GPS satellites may be in error. The resulting
GPS position may be in error beyond the limits allowed
for your current phase of flight. Cross-check your position
with an alternate navigation source. If the warning occurs
during a final approach segment (FAF to MAP), execute the
published missed approach.
Scheduler message [1-9] — [user entered text] —
The
user-entered scheduler message time has expired, and the
scheduler message is displayed.
Searching the sky — The 400W-series unit is searching the
sky for GPS satellites.
Select appropriate frequency for approach — You are
inbound and within 3 NM of the FAF; and the active VLOC
frequency does not match the published frequency for the
approach. Tune the standby VLOC frequency to the proper
frequency and press the
VLOC flip-flop key to “activate”
the frequency.