����ý

NGT-9000 is: EB2

NGT-1000 is: U1

NGT-2000 is: U2

NGT-2500 is: U2

TAS – Traffic Advisory Systems are a Transponder-based active traffic system that displays traffic from transponder equipped aircraft. This is an add-on feature for Lynx which requires both an additional Directional antenna (NY-156/-164), and a feature unlock code.

ATAS – ADS-B Traffic Advisory System is simply audio alerting of High-Threat ADS-B traffic. This is standard on the Lynx beginning with software 3.2, but the feature must be enabled in the DCM in order to work.

1. The NGT-9000, also referred to as the “straight” NGT-9000, includes an internal position source (WAAS GPS), 1090ES Transponder for the transponder and the ADS-B Out functions, Dual-Band ADS-B In which gives you the FIS-B weather products and the ADS-B traffic. Additionally it includes the PIM-9000 WiFi module for displaying this information on a PED via various Aviation Apps.

2. The NGT-9000+, has ALL the same functionality of the straight NGT-9000, Plus it adds TAS/TCAS1 active traffic. This requires the additional NY-156/-164 directional antenna.

3. The NGT-9000D, has ALL the same functionality of the straight NGT-9000, and, it adds the Diversity function. This requires an additional L-Band antenna to be mounted on-top.

4. The NGT-9000D+, has ALL the same functionality of the straight NGT-9000, as well as the NGT-9000D and the NGT-9000+. It also requires the NY-156/-164 Directional antenna, but not the additional L-Band antenna, because the Top Diversity antenna function is incorporated in the NY-156/-164.

1. You can display all traffic that the lynx displays via the ARINC 429 interface. All symbology will be TAS symbols and not ADS-B symbols.

2. You cannot display the FIS-B Weather products because Garmin uses a proprietary Buss for all weather inputs.

No, Garmin has not/will not develop the interface for that.

No, Garmin has not/will not develop the interface for that.

• There are a couple of things that can cause this message when the Light sensor is actually functioning correctly. To verify proper Light sensor functionality, do the following:

• To check to see if the sensor works: set the brightness to ~40% using the onscreen menu (Traffic screen/Options/Settings/BRT), cover up the sensor for ~15 secs, and then immediately shine a light on it, it will get bright very quickly which should be easy to see. The ramp up rate is much faster than the ramp down.

• A mis-wired or malfunctioning DCM can also cause this message.

The vast majority of the time this is because the unit isn’t seating in the mounting rack completely:

1. Remember that it takes a full 40 turns of the locking mechanism from fully extended to fully retracted.

2. The lower horizontal lip of the mounting tray MUST stand out from the instrument panel slightly. If it is flush with the instrument panel the unit will NOT seat fully.

3. REFER TO SL-306.

4. If this is a new installation, confirm the DCM is correctly pinned into the connector.

1. We do not charge for the software.

2. If you go to an authorized L3Harris Dealer or Aspen Dealer, they can submit a warranty claim. For Lynx software upgrades to version 3.2.1 or 3.2.2 we will reimbursement the Dealer for up to 1 hour of labor. Bear in mind that the man-hours will vary according to the shop’s level of experience with Lynx.

1. First check to see if your iPad is still connected to the “LYNX WiFi network” – go to the iPad Settings/WiFi and look for the connection. If it is still connected then the PIM-9000 WiFi Module is working and the problem is most likely with the App.

2. Some Apps behave marginally when there are a lot of background apps running. Double click the iPad Home button, and then swipe off all the background Apps.

3. If this problem continues with another iPad or another App it is possible that the PIM-9000 WiFi module is bad.

This is merely a very poorly worded Foreflight message telling you that you only have X number, or less, ground stations being received. It by no means is any indication of the Lynx performance.

At this point in time, they have not been incorporated into the Lynx software, so, No, as of now. The good news is that all this data is passed directly through to the WiFi module and is broadcast to the PED/Apps for display.

• The System Status Messages are actually quite accurate and helpful for troubleshooting, but, make sure it is recorded correctly (a photo is best). For example, there is a BIG difference between the messages: “Transponder Fail” and “Transponder External Fail”.

• In the Installation manual, chapter 4, tables 4-1 & 4-2, and in the Pilot’s Guide, chapter 5, table 5-1, have a listing of the messages in a “Symtom/Cause/Corrective Action format that is very helpful.

1. With the MPC connected to the NGT-9000, in the “Maintenance No WiFi” mode, from the main page, go to “File”, “Save”, and then name the file with the N# and date – N1234R071619 for example. Then email it to: CRC.ACSS@L3Harris.com.

2. Saving from the main MPC page ensures we will get ALL the MPC data.

With the MPC connected to the NGT-9000, in the “Maintenance No WiFi” mode, on the Fault Log page, click on an Index line and it will become highlighted. Note that at the top there is a “Fault Description” and a “Loss of Functionality” box. The Fault Description tells what triggered this fault, and the Loss of Functionality is usually the same as the System Status Message shown on the Lynx, and this is very helpful for troubleshooting especially when it is combined with the explanation of the System Status messages in Chapter 4 tables 4-1 & 4-2.

The majority of time this is because the unit is not seeing a consistent power bus level. If the unit has 200 msec power drops or marginal supply levels, this symptom can occur. To troubleshoot:

1. If the Lynx is on a separate circuit breaker, power off other units on the same breaker.

2. Now power off the Lynx for at least 1 second.

3. Power the Lynx back on independent of other bus sources. If the problem is no longer present, there is a strong potential that the bus sharing is driving the bus lower than a 10 V level at the unit for short periods of time. Consider the current capability of the external supply to the unit.

4. If the unit continues to show this message despite having a sole use of the bus, the product may have an internal fault. View the fault log and use this as a basis to potentially return the unit.

1. This may not be a high temperature condition. The Lynx may not being able to sense the internal temperature for an extended period of time (~ 60 seconds). This symptom can sometimes occur with sudden power loss and return in < 1 second intervals.

2. If this message is seen at around 60 seconds after power on and is seen with Ambient Light Sensor fail and possibly with ATAS Unavailable or ADS-B In Unavailable, it is likely this particular case.

3. If on ground, the recommended response is to power off the Lynx and leave it unpowered for 15 seconds. Upon the next power on, this problem should clear. If the problem does not clear, the unit likely has an internal fault occurring and should be returned.

4. If in air, normal XPDR functionality is maintained during this mode and the unit’s power cycle should occur after landing per the above step.

5. If this message is seen well after 60 seconds beyond powering on, check if the unit may be overheating with a quick tap on the display screen if possible. The unit temperature should not be hot to the touch, but may be subject to this condition in the event of a failure. If unusually hot, an internal failure is likely and the unit should be returned.

6. If this repeatedly occurs, and the message remains On, it would be advisable to have the fault log checked for fault messages and the actual temperature recorded.

1. Make sure the plane is outside of the hangar and has a clear view of the sky (minimize building obstructions).

2. Verify GPS S/W is loaded using MPC tool on the Versions page. The composite part number should be 9021105-012 or later. If this version is not loaded, load per steps 19-38 found in Service Bulletin SB 9029000-10.

3. Observe the GPS Receiver Information MPC (Service – GPS) for correct signal strength (C/No) of the GPS satellites. This has a range from 30 dB to 50 dB. If the values obtained are not in this range, then check if the antenna cable loss is more than 10 dB.

4. Check if 12V power is available at GPS antenna port, when the unit is powered on. This voltage has a tolerance of 10.8 V to 13.2 V.

This can occur when the configuration setting within the Detachable Configuration Module (DCM) is set for a remote mount unit, but your unit is Panel Mount. To correct this:

1. Do a screenshot of each page of your configuration settings.

2. Then, in Maintenance Mode, go to Setup -> Restore -> Restore Installation Configuration (DCM) Defaults and press “Set Defaults”.

3. Then, re-enter your configuration settings and Apply.

4. The left hand panel Transponder page will once again accept entries.