Why won't my Garmin GNC 355 GPS 175 OBS resolver calibrate?
If your Garmin GPS 175 OBS resolver won't calibrate, the issue is likely due to an incompatible resolver or an improper connection. Check the resolver specifications and wiring to ensure they are correct.
What to do if my Garmin GNC 355 GPS/GNX/GNC does not compute position?
If your Garmin GPS 175, GNX 375, or GNC 355 is not computing its position, the issue might be due to inadequate GPS signals. Check the GPS antenna connections to ensure they are secure. Also, make sure the aircraft is in a location free from obstructions such as hangars, buildings, or trees.
Why does Garmin GNC 355/GNX/GNC signal drop when avionics are turned on?
If the GPS signal level of your Garmin GPS 175, GNX 375, or GNC 355 drops when avionics are turned on, it's likely due to noise interference from other avionics. To address this, turn off all other avionics and then turn them back on one at a time to identify the source of the interference. Reroute the GPS cable and reposition the GPS antenna away from the interfering unit.
Why are Garmin GNC 355 GPS signal levels very low?
If the GPS signal levels on your Garmin GNC 355 are very low, this could be due to several reasons. First, check the GPS antenna installation, connections, and cable routing, ensuring the antenna is mounted on top of the aircraft. Second, ensure the aircraft is clear of obstructions like hangars, buildings, or trees. Third, RF interference at 1575.42 MHz from VHF COM can be the cause. Add a 1575.42 MHz notch filter in COM coaxial. Fix or replace the COM. Disconnect the ELT antenna coaxial to check for possible re-radiation. Move GPS antenna further from the COM antenna.
Why are Garmin GNC 355 GPS 175 GPS signal levels very low?
If the GPS signal levels on your Garmin GPS 175 are very low, it could be due to improper antenna installation or the antenna being shaded. Check the GPS antenna installation, connections, and cable routing, ensuring the GPS antenna is mounted on the top of the aircraft. Also, make sure the aircraft is clear of obstructions like hangars, buildings, or trees.
How to adjust COM sidetone level on Garmin GNC 355?
If the COM sidetone level on your Garmin GNC 355 is too low or too high, it could be due to using the wrong type of headsets or because the sidetone level needs adjustment. If necessary, adjust the sidetone level on the COM Setup Config Mode page.
How to correct incorrect Mode S aircraft data transmitted by Garmin?
If your Garmin system is transmitting incorrect Mode S aircraft data, the problem might be an incorrect Flight ID configuration. Check the Flight ID Configuration page and verify that the settings are configured correctly.
Why does Garmin GNC 355 COM not transmit?
If the Garmin GNC 355 COM does not transmit, there might be several reasons: 1. The PTT input is not being pulled low. Check that the MIC 1 Transmit (P3552-11) input is pulled low for transmit; the state of this discrete input can be monitored on the Discrete Inputs page found on the GNC Diagnostics page. 2. There is no transmit power to COM. Ensure power input is connected to the COM 44-pin connector P3552—30, -43, and -44, and ground to P3552-37, -38, and -40. 3. The input voltage is too low. Increase the input supply voltage to >11VDC.
Why is my Garmin GNC 355 not receiving heading from compass system?
If your Garmin GNC 355 is not receiving heading from the compass system (ARINC 429 heading input), this could be due to an incorrect ARINC 429 input speed setting or incorrect wiring connections. Check the ARINC 429 input port speed setting for the device and verify it is correct. You should also check the wiring connections; the raw data being received by the GNC 355 can be monitored on the ARINC Inputs page found on the Diagnostics page.
Why is my Garmin GNC 355 175 not receiving heading from compass system?
If your Garmin GPS 175 is not receiving heading from the compass system (ARINC 429 heading input), it could be due to an incorrect ARINC 429 input speed setting or incorrect wiring connections. Verify the ARINC 429 input port speed setting for the connected device. Also, check the wiring connections; the raw data received by the GPS 175 can be monitored on the ARINC Inputs page found on the Diagnostics page.
General description of the GPS 175, GNC 355/355A, and GNX 375 navigators and their features.
Details the physical components and controls of the unit, including bezel, touchscreen, knobs, and keys.
Lists required and optional Line Replaceable Units (LRUs) and interfaces compatible with the system.
Describes the initial power-on sequence, software versions, and database status checks.
Explains database updates via SD card or Flight Stream, supported types, and effective cycles.
Details how Connext works via Bluetooth, enabling features like GPS position and flight plan transfer.
Explains the map display features, aircraft symbol, track vector, basemap, and overlays.
Details how current flight plan information is displayed as a scrolling list on the Active Flight Plan page.
Explains how to set a course to any waypoint using the Direct To function with various selection methods.
Describes database and user waypoints, including search functions and specific page features.
Explains how to load and manage departure, arrival, and approach procedures for flight plans.
Describes how to calculate time to TOD and vertical speed required to reach a target altitude.
Explains how to view and compute fuel conditions along a flight plan or between waypoints.
Details how to calculate density altitude, true airspeed, and winds based on input variables.
Explains how to determine GPS coverage availability and predict fault detection integrity.
Covers FIS-B weather products, display, data limitations, and reception.
Explains ADS-B In traffic applications (AIRB, ATAS, SURF), features, and display.
Details terrain and obstacle depictions, including color shading, proximity, and alerting functions.
Explains system-related messages, their display, logging, and message key.
Lists advisories related to database issues, their conditions, and corrective actions.
Covers advisories for flight plan import, storage, and changes, with corrective actions.
Details advisories for GPS receiver issues, loss of integrity, and navigation errors.
Lists advisories for hardware faults, temperature issues, data loss, and component failures.
Explains how to qualify gloves for touchscreen use, including selection considerations and guidance.
States that the Garmin unit meets FAA AC 90-100A requirements for RNAV operations.
General| Channels | 200 |
|---|---|
| Interface | RS-232 |
| GPS Receiver | WAAS |
| Connectivity | Bluetooth |
| Display Type | Color |
| Approaches | LPV/LNAV/VNAV/GPS |
To Next Page
