Lynx® ADS-B In / Out Transponder and Display System

1. Request an account from the ACSS Tech Pub site (link below)

2. When you apply, request permissions for Lynx, Lynx 9000 Software, and MPC.

3. You will automatically be notified about updates/Revisions to whichever product documents you subscribe to when they occur.

1. Ref: Service Bulletin SB9029000-7.

2. Installation of S/W 3.1 resolves this issue.

1. Ref: Service Bulletin SB9029000-7.

2. Most likely when loading the new GPS S/W file the load was either interrupted or canceled before the file had completed loading. The GPS S/W file takes much longer to load than the Flight S/W and you must run the loading procedure until the MPC screen tells you that the load has been successful before changing pages or cycling power.

1. Ref: Service Bulletin SB9029000-10.

2. The UAT-MSS.bin file did not get loaded, or –

3. It is likely when loading the new GPS S/W file the load was interrupted or canceled prior to completion. The GPS S/W file takes much longer to load than the Flight S/W and you must run the loading procedure until the MPC screen tells you that the load has been successful before changing pages or cycling power.

4. You MUST verify the new load prior to Returning To Service.

• This can be done with either the MPC tool, or the start-up screen.

It is generally accepted that the operator updating operational software with the MPC tool does not fall under the definition of Part 43 Preventative Maintenance. You could do this under the direct supervision of an A&P/IA who would then make a logbook entry of the work that was performed and sign it off as returned to service.

• Beginning with S/W Rel 2.0, all three databases are required for the NGT-9000 to operate correctly – 68DC Airport, 72DC Map, and 71DC Terrain. Terrain is required for various background functions, even if you do not use the TerrainVision or TAWS functions.

• There is no required database update period.

• Databases must be purchased from Jeppesen. Cost for a one-time update of all three databases is reportedly around $135. Reference paragraph 1.12.1 in the NGT-9000 Installation Manual, P/N 0040-17001-01, for ordering information.

• When downloading from Jeppesen and loading to the NGT-9000, according to Jeppesen: “Unfortunately there is no way to transfer this data from JDM directly to your PC. JDM looks for a specific type of media to transfer to based off each Avionics type. For the L3 NGT-9000 it expects a USB drive formatted to FAT32, and it won’t transfer to anything but that.” It has been reported it will also transfer to an SD card formatted to FAT32.

• The computer you use for this must be an American/English based computer.

1. Ref: Para. 1.9, Software Revisions in the NGT-9000 Installation Manual, P/N 0040-17001-01.

2. The Service Bulletin appropriate for the Software you are installing will also reference the correct MPC.

1. Ref: Para. 3.4 in the NGT-9000 Installation Manual, P/N 0040-17001-01.

2. Most likely the USB Driver has not been installed on the MPC you are using.

3. The Zadig USB Driver (for Win 7, 8, and 10) must be installed before you can communicate with the Lynx

• You can get this driver from the ACSS Tech Pub site: (link below)

• or, simply download it by Googling “Zadig USB Driver”

4. When installing this driver you MUST be connected to the NGT-9000 with a data cable and the installer program MUST recognize the NGT-9000.

5. Make sure you are using a known good USB DATA CABLE!

6. If this driver has been installed and you have difficulty connecting and do not see any message windows, try closing and then reopening the MPC S/W and cycling power to the NGT.

1. Ref: Para. 1.9, Software Revisions, in the NGT-9000 Installation Manual, P/N 0040-17001-01, or the Service Bulletin if you are trying to update software.

2. You need a different (higher) revision of the MPC S/W. The latest MPC S/W will always work with all previous NGT S/W revisions.

1. Windows XP is NOT supported by MicroSoft anymore, and as a result is too unstable for satisfactory results with the MPC tool S/W. We do not support Win XP with our MPC S/W.

2. Win 7, 8, and 10 all work, but Win 10 is preferred.

YES you can. Reference Appendix C of the NGT-9000 Installation Manual, P/N 0040-17001-01, for an interconnect drawing.

We will Need:

1. The Enhancement Certificate # (or a scanned copy of the certificate), or the P.O. or Sales Oder that it was purchase under.

2. The Tail Number of the aircraft.

3. The Modes S Identifier (ICAO Code) in OCTAL form –this is especially true of foreign registered aircraft.

4. Point of Contact to Order:

Order Administration

Telephone: +1 623-445-7040

1. Double check that the Tail Number and the Mode S Identifier numbers provided are correct.

2. Double check that the Mode S Identifier numbers are correctly entered in the Configuration and that there are NO spaces. This must be an 8-digit OCTAL Number.

3. When all else fails, just start over getting a new code.

Ref: Para. 3.7.1, Table 3-1 in the NGT-9000 Installation Manual, P/N 0040-17001-01.

1. Ref: Para. 3.10.1 in the NGT-9000 Installation Manual, P/N 0040-17001-01.

2. Is the MPC connected to the NGT with the Data Cable? If Yes, that is your problem. You must be connected to the WiFi Module Wirelessly.

No

1. Not if you have a good 6 feet of separation between the NGT antenna and other L-band antennas.

2. In the case of Non-TSO’d DMEs, such as B/K Silver Crown DMEs, definitely do NOT connect the Suppression Line between the two units, you must move one of the antennas so you have at least 6 feet of separation. This is because B/K uses a non-standard suppression signal levels.

You can go directly from 1.X to the latest S/W Revision, however, when passing 2.0 S/W you will lose the databases and will need to purchase ALL THREE database from Jeppesen – see NGT-9000 Installation Manual, P/N 0040-17001-01, para. 1.12.1

1. NGT-9000 – need two, usually one TNC & one BNC – This is included in all Install Kits.

2. NGT-9000D – one additional pigtail assembly is required, for the additional top antenna.

3. NGT-9000+ and NGT-9000D+ – requires 3 additional pigtail assemblies.

4. The installer must specify straight or right-angle plugs, as well as TNC or BNC Jacks.

5. Ref. Table 1-17 in the NGT-9000 Installation Manual, P/N 0040-17001-01, for Part Number information.

The NGT must be in the Maintenance mode in order to test the transponder – use the MPC S/W tool (Service), or from the front panel of the unit. Ref. NGT-9000 Installation Manual, P/N 0040-17001-01, Para. 3.5.

1. You need to be in the Ground Test Mode in order to perform the transponder tests.

2. There are two was of getting into the ground Test Mode, One is using the MPC and selecting Ground Test when restarting, and the second way is without the MPC and using the touch screen itself. Ref. para. 3.5 of the NGT-9000 Installation Manual, P/N 0040-17001-01, and it will tell you how to do this from the front panel of the NGT-9000.

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.