536
edits
LINK 16: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
| style="background-color:#fe0000;" | | | style="background-color:#fe0000;" | | ||
| Donor | | Donor | ||
| style="text-align:center; font-weight:normal;" | | | style="text-align:center; font-weight:normal;" | Yes<br />But donor secondary fighter air target tracks, lock lines and AMRAAM shot lines not yet implement. | ||
| style="font-weight:normal;" | | | style="font-weight:normal;" | For situational awareness during a mission, pilots may want to monitor aircraft or targets reported by aircraft that aren’t part of their flight or team. These aircraft, known as donors, can be designated during mission planning (via the Data Cartridge), or selection or deselection can be managed in the cockpit through the LINK 16 DNR page on the DED. | ||
|- | |- | ||
| FC | | FC | ||
| Line 47: | Line 47: | ||
| style="text-align:center; font-weight:normal;" | Yes | | style="text-align:center; font-weight:normal;" | Yes | ||
| style="font-weight:normal;" | This Channel establishes the subnet on the C2 (e.g. AWACS or ABCCC) aircraft is operating. The control NPG is used by C2 to transmit assignments to the flight lead and for the flight lead to transmit responses and report assignment status. As a flight progresses to the target area, the controlling aircraft could change. When a controller change is required, the current controlling aircraft transmits a request for handover message to the flight indicating the new controllers subnet (i.e., MC). After accepting the handover request, the flight members change the mission channel to communicate with the new controller. The numerical value can be set between 0 and 127. | | style="font-weight:normal;" | This Channel establishes the subnet on the C2 (e.g. AWACS or ABCCC) aircraft is operating. The control NPG is used by C2 to transmit assignments to the flight lead and for the flight lead to transmit responses and report assignment status. As a flight progresses to the target area, the controlling aircraft could change. When a controller change is required, the current controlling aircraft transmits a request for handover message to the flight indicating the new controllers subnet (i.e., MC). After accepting the handover request, the flight members change the mission channel to communicate with the new controller. The numerical value can be set between 0 and 127. | ||
|- | |||
| MIDS | |||
| Multifunctional Information Distribution System | |||
| style="text-align:center; font-weight:normal;" | Yes | |||
| style="font-weight:normal;" | See JTIDS | |||
|- | |- | ||
| NDL | | NDL | ||
| Network Design Load | | Network Design Load | ||
| style="text-align:center; font-weight:normal;" | Yes | | style="text-align:center; font-weight:normal;" | Yes | ||
| style="font-weight:normal;" | | | style="font-weight:normal;" | This system used to initialize the JTIDS/MIDS terminal | ||
|- | |- | ||
| NPG | | NPG | ||
| Line 61: | Line 66: | ||
| Precise Participant Location and Identification | | Precise Participant Location and Identification | ||
| style="text-align:center; font-weight:normal;" | Yes | | style="text-align:center; font-weight:normal;" | Yes | ||
| style="font-weight:normal;" | | | style="font-weight:normal;" | This message transmission from LINK 16 air participants, furnishing network participation status, identification details, positional data and navigation information. It encompasses the voice call sign, position coordinates (latitude/longitude), altitude, course, IFF codes, air platform type (e.g. fighter, bomber, attack) and air platform activity (such as engaging, investigating etc.). PPLI air tracks are shared between aircraft sharing the same NPG. | ||
|- | |- | ||
| SC | | SC | ||
| Line 71: | Line 76: | ||
| Surveillance | | Surveillance | ||
| style="text-align:center; font-weight:normal;" | Yes | | style="text-align:center; font-weight:normal;" | Yes | ||
| style="font-weight:normal;" | | | style="font-weight:normal;" | This message serves to share air track data, predominantly disseminated by a Command and Control agency. It comprises details regarding exercise/non-exercise tracks including; track number, strength, position, speed, course, identity (such as pending, unknown, assumed friend, friend, neutral, suspect, hostile), IFF codes, air platform type (generic categories like fighter, bomber, attack etc.) and specific air platform type (e.g. F15, F16 Mig29 etc.). | ||
|} | |} | ||