Jak/Sandbox - Revision history

Jak at 04:13, 5 May 2021

2021-05-05T04:13:27Z

← Older revision		Revision as of 04:13, 5 May 2021
Line 1:		Line 1:
	Basic A/A Systems Operation<br>		Basic A/A Systems Operation<br>
	The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.		The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.

			<!--Although the Radar is the most important and useful sensor generally, other sensors can also provide inputs to MSI targets.

			The Forward Looking Infrared (FLIR) provides angle-only information on a target while in Autotrack. If not correlated with the Radar, the Autotrack target appears as an angle-only trackfile (AOT) HAFU symbol with a letter "F" in place of the altitude. If both the FLIR and Radar are contributing to the same target then it will mostly appear like any other Radar trackfile.

			The Link 16 Datalink network is also an MSI contributor. Three Link 16 net groups provide targets: Precise Participant Location and Identification (PPLI), Fighter-to-Fighter (F/F), and Surveillance (SURV). The PPLI group consists of friendly trackfiles broadcasted by the aircraft themselves. F/F consists of any targets from other fighter-type aircraft. SURV consists of any targets from other surveillance-type aircraft like AWACS as well as ground- and sea-based radar systems. The cuing for Datalink trackfiles is detailed under HAFU Symbology, but generally the existence of a "upside down" HAFU shape indicates that Datalink is a contributor to an MSI trackfile.

			The Combined Interrogator/Transponder (CIT) is used to send IFF interrogations at existing MSI trackfiles. A manual interrogation can be shot at an individual MSI track using the cursor on the Attack, Az/El, or SA formats. Pressing the Castle switch down (depress) and then right shoots the interrogation. Automatic interrogation settings are available on the Az/El format.-->

	'''Radar/Attack format.''' The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.		'''Radar/Attack format.''' The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.

Jak at 12:38, 4 May 2021

2021-05-04T12:38:20Z

← Older revision		Revision as of 12:38, 4 May 2021
Line 4:		Line 4:
	'''Radar/Attack format.''' The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.		'''Radar/Attack format.''' The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.

	'''Multi-Sensor Integration trackfiles.''' Most targets displayed are MSI trackfiles. The exception is raw Radar hits which are the raw returns of the Radar ~~only (~~green ~~bricks)~~. An MSI trackfile ~~can be contributed to by~~ the ~~Radar and/or by Datalink. Each track~~ is a single sensor-fuzed target which may have only Radar, only Datalink, or both Radar and Datalink ~~contributing to it~~.		'''Multi-Sensor Integration trackfiles.''' Most targets displayed to the pilot are MSI trackfiles. The only exception is raw Radar hits which are the raw returns of the Radar, represented by green brick symbols. These hits are not correlated or extrapolated; hence, "raw" hits. An MSI trackfile on the other hand is a single sensor-fuzed target which the Radar may or may not be contributing to. An MSI track may have only Radar, only Datalink, or both Radar and Datalink contribution.

	An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). A HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track ~~will have~~ an "upside up" HAFU symbol along with an upside down one to indicate any type of Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently based on the contributors. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV) track appears as a ~~smaller~~ HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.		An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). The HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track has an "upside up" HAFU symbol along with an upside down one to indicate any type of Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently based on the contributors. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV)-only track appears as a 1/2-size HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.

	'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).		'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).

Jak at 20:45, 30 April 2021

2021-04-30T20:45:59Z

← Older revision		Revision as of 20:45, 30 April 2021
Line 14:		Line 14:
	'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS. The difference is that in RWS, most trackfiles are intentionally hidden. It is important to note they still exist even when they are hidden. There are a few ways these trackfiles are displayed.		'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS. The difference is that in RWS, most trackfiles are intentionally hidden. It is important to note they still exist even when they are hidden. There are a few ways these trackfiles are displayed.

	If designated as the L&S or DT2 target, ~~a trackfile~~ is displayed as a HAFU symbol with its Mach number and altitude to the left/right. In the case of a Radar ~~track~~ it is displayed ontop of the corresponding hits.		If a trackfile is designated as the L&S or DT2 target, it is displayed as a HAFU symbol with its Mach number and altitude to the left/right. In the case of a Radar trackfile, it is displayed ontop of the corresponding hits.

	Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option.		Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option.

Jak at 20:41, 26 April 2021

2021-04-26T20:41:50Z

← Older revision		Revision as of 20:41, 26 April 2021
Line 6:		Line 6:
	'''Multi-Sensor Integration trackfiles.''' Most targets displayed are MSI trackfiles. The exception is raw Radar hits which are the raw returns of the Radar only (green bricks). An MSI trackfile can be contributed to by the Radar and/or by Datalink. Each track is a single sensor-fuzed target which may have only Radar, only Datalink, or both Radar and Datalink contributing to it.		'''Multi-Sensor Integration trackfiles.''' Most targets displayed are MSI trackfiles. The exception is raw Radar hits which are the raw returns of the Radar only (green bricks). An MSI trackfile can be contributed to by the Radar and/or by Datalink. Each track is a single sensor-fuzed target which may have only Radar, only Datalink, or both Radar and Datalink contributing to it.

	An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). A HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track will have an "upside up" HAFU symbol along with an upside down one to indicate Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV) track appears as a smaller HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.		An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). A HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track will have an "upside up" HAFU symbol along with an upside down one to indicate any type of Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently based on the contributors. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV) track appears as a smaller HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.

	'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).		'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).
Line 12:		Line 12:
	'''Scan volume/centering.''' The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.		'''Scan volume/centering.''' The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.

	'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, ~~though they~~ are ~~mostly~~ hidden ~~on purpose~~. It is important to note they still exist even if they are hidden. There are a few ways ~~a trackfile is~~ displayed:		'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS. The difference is that in RWS, most trackfiles are intentionally hidden. It is important to note they still exist even when they are hidden. There are a few ways these trackfiles are displayed.

	If designated, a trackfile ~~will always be~~ displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but just the display on the Attack format in RWS.		If designated as the L&S or DT2 target, a trackfile is displayed as a HAFU symbol with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits.

			Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option.

			For any trackfile not being displayed, the pilot can 'preview' it by slewing the cursor over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS not selected, cursoring over a raw Radar hit will not display a trackfile; instead it just displays the raw hit's altitude to the right of the cursor. Once a track is cursored over with the LTWS function, it can be designated by depressing the TDC to permanently display it.

			Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but just the display on the Attack format in RWS.

	'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.		'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.

Jak at 22:31, 10 April 2021

2021-04-10T22:31:28Z

← Older revision		Revision as of 22:31, 10 April 2021
Line 20:		Line 20:
	'''SA format.''' The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.		'''SA format.''' The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.

	'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. ~~The~~ DT2 and L&S can be quickly ~~switched~~ with the Undesignate button. Both the L&S and DT2 positions are ~~superimposed~~ on the HUD and HMD~~; the~~ L&S is a box and the DT2 is an "X" shape.		'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. Also, the DT2 and L&S can be quickly swapped with the Undesignate button. Both the L&S and DT2 positions are shown on the HUD and HMD. The L&S is a box and the DT2 is an "X" shape.

	'''Designation methods.''' To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.		'''Designation methods.''' To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.
Line 28:		Line 28:
	'''Entering Track While Scan (TWS) and Single Target Track (STT).''' Once the target or targets of an attack are detected and identified, it is usually desired to more closely track them. This is generally done by way of the Track While Scan (TWS) or Single Target Track (STT) modes. The transition is smooth since trackfiles are already being made in RWS. TWS can be entered via the mode option at PB5 using the pushbutton or via cursor. STT can be entered from RWS or TWS in a few ways, all termed methods of "acquisition". The most common method is Fast Acquisition whereby the desired trackfile or hit is placed under the cursor and the Sensor Control switch is bumped toward the Attack format. This also works on the Az/El format.		'''Entering Track While Scan (TWS) and Single Target Track (STT).''' Once the target or targets of an attack are detected and identified, it is usually desired to more closely track them. This is generally done by way of the Track While Scan (TWS) or Single Target Track (STT) modes. The transition is smooth since trackfiles are already being made in RWS. TWS can be entered via the mode option at PB5 using the pushbutton or via cursor. STT can be entered from RWS or TWS in a few ways, all termed methods of "acquisition". The most common method is Fast Acquisition whereby the desired trackfile or hit is placed under the cursor and the Sensor Control switch is bumped toward the Attack format. This also works on the Az/El format.

	'''Track While Scan (TWS).''' In TWS mode, the scan volume is ~~limited~~ to maintain a scan frame time of 3 seconds or less which results in a high trackfile refresh rate. Note that there is no difference in trackfile processing between RWS and TWS, but TWS simply provides better tools for attacking targets. In TWS, raw hits can be displayed like in RWS, but all trackfile HAFU symbols are also always displayed. Unlike RWS, raw hits can be removed in TWS by unboxing the HITS option at PB8. This makes the display less cluttered.		'''Track While Scan (TWS).''' In TWS mode, the scan volume is restricted to maintain a scan frame time of 3 seconds or less which results in a high trackfile refresh rate. Entering TWS from RWS may result in a smaller volume being forced. Note that there is no difference in trackfile processing between RWS and TWS, but TWS simply provides better tools for attacking targets. In TWS, raw hits can be displayed like in RWS, but all trackfile HAFU symbols are also always displayed. Unlike RWS, raw hits can be removed in TWS by unboxing the HITS option at PB8. This makes the display less cluttered.

	'''TWS scan centering.''' One highly important TWS tool is AUTO scan centering, which automatically adjusts the Radar scan center to keep the L&S and DT2 trackfiles in the scan volume. In AUTO, the pilot retains the ability to "bias" the scan ~~volume~~ as desired while maintaining the L&S/DT2. This biasing is accomplished using the cursor just like in manual centering. Fully manual (MAN) scan centering is also available in TWS which functions ~~just like in~~ RWS. TWS first defaults to MAN if entered from RWS or VS. AUTO ~~is default when entering TWS~~ from STT. An AUTO/MAN toggle is available at PB13.		'''TWS scan centering.''' One highly important TWS tool is AUTO scan centering, which automatically adjusts the Radar scan center to keep the L&S and DT2 trackfiles in the scan volume. This allows the pilot to focus less on manipulating the scan while engaging targets. While in AUTO, the pilot retains the ability to manually "bias" the scan center as desired, while still automatically maintaining the L&S/DT2. This biasing is accomplished using the cursor just like with manual centering. Fully manual (MAN) scan centering is also available in TWS which functions identically to RWS. TWS first defaults to MAN if entered from RWS or VS or to AUTO if entered from STT. An AUTO/MAN toggle is available at PB13.

	'''Single Target Track (STT).''' STT operation is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, especially important for weapon guidance, at the cost of the Radar ~~not scanning any volume of space at all~~. The STT RAID mode is available for toggle via the RAID switch on the throttle. In RAID the Radar alternates between full track and brief scans where it searches for additional targets in a narrow vicinity of the STT target. A zoomed in 5nm x 5nm display ~~is provided in RAID~~.		'''Single Target Track (STT).''' STT operation is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, which is especially important for weapon guidance, at the cost of no space being scanned by the Radar. The STT RAID mode is available for toggle via the RAID switch on the throttle. In RAID, the Radar alternates between full track and brief scans where it searches for additional targets in a narrow vicinity of the STT target. In RAID the Attack format is zoomed in to a 5nm x 5nm display centered on the STT target.

	'''Exiting STT.''' Return to Search (RTS) from STT ~~can be~~ done by pressing the Undesignate button. The Radar returns to ~~TWS if~~ STT ~~was entered from~~ TWS or ~~RWS if it was entered from RWS or VS~~. The Radar ~~doesn't return~~ to VS since this would delete the existing trackfile. ~~The~~ Radar ~~also~~ returns to TWS ~~regardless~~ if an AMRAAM is in flight. The mode that will be commanded is indicated at PB5 under the word "RTS". There is also a TWS option at PB10 to go to TWS directly from STT.		'''Exiting STT.''' Return to Search (RTS) from STT is most easily done by pressing the Undesignate button. The Radar returns to the mode used to enter STT (which can be RWS, TWS, or an ACM mode). There are a few exceptions. The Radar never returns to VS since this would delete the existing trackfile. Also, the Radar always returns to TWS if an AMRAAM is in flight. The mode that will be commanded upon RTS is indicated at PB5 under the word "RTS". There is also a TWS option at PB10 to go to TWS directly from STT in any scenario.

	'''AMRAAM and Sparrow missiles.''' The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles which are highly integrated with the Radar. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular illuminating waveform picked up by the Sparrow seeker. This guidance requires STT, so the Sparrow can only be guided at one target at once, and only in STT. The AMRAAM uses one-way datalink transmissions from the Radar for the majority of the its flight to the target, which can be supplied in RWS, TWS, or STT. This means the AMRAAM can be employed at many targets simultaneously. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. An AMRAAM launch from RWS automatically commands TWS, but RWS could be reselected if ultimately desired. Also, if STT is entered from RWS and an AMRAAM is fired, the Return to Search (RTS) mode becomes TWS, even though STT was entered from RWS.		'''AMRAAM and Sparrow missiles.''' The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles which are highly integrated with the Radar. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular illuminating waveform picked up by the Sparrow seeker. This guidance requires STT, so the Sparrow can only be guided at one target at once, and only in STT. The AMRAAM uses one-way datalink transmissions from the Radar for the majority of the its flight to the target, which can be supplied in RWS, TWS, or STT. This means the AMRAAM can be employed at many targets simultaneously. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. An AMRAAM launch from RWS automatically commands TWS, but RWS could be reselected if ultimately desired. Also, if STT is entered from RWS and an AMRAAM is fired, the Return to Search (RTS) mode becomes TWS, even though STT was entered from RWS.

Jak at 08:37, 6 April 2021

2021-04-06T08:37:28Z

← Older revision		Revision as of 08:37, 6 April 2021
Line 1:		Line 1:
	Basic A/A Systems Operation<br>		Basic A/A Systems Operation<br>
	The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.		The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.

			'''Radar/Attack format.''' The primary Radar interface is the Attack format. In addition to being accessible from the TAC menu, it can be accessed via HOTAS by bumping the Castle switch right. This invokes the format on the right DDI. The same occurs when entering A/A master mode.

			'''Multi-Sensor Integration trackfiles.''' Most targets displayed are MSI trackfiles. The exception is raw Radar hits which are the raw returns of the Radar only (green bricks). An MSI trackfile can be contributed to by the Radar and/or by Datalink. Each track is a single sensor-fuzed target which may have only Radar, only Datalink, or both Radar and Datalink contributing to it.

			An MSI trackfile is represented by a symbol called a HAFU ("Hostile, Ambiguous, Friendly, or Unknown"). A HAFU is shaped like a triangle for a hostile, a staple for an unknown or ambiguous, or a half circle for a friendly. It is also colored red, yellow, or green accordingly. A Radar MSI track will have an "upside up" HAFU symbol along with an upside down one to indicate Datalink contribution, if any. An MSI track with only Datalink contribution will appear differently. If it has Fighter-to-Fighter (F/F) contribution then it appears simply as an upside down only HAFU. A Surveillance (SURV) track appears as a smaller HAFU and either a diamond, tall/skinny rectangle, or full circle. A Precise Participant Location and Identification (PPLI) track appears as a full-sized full circle.

	'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).		'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).

Jak at 07:40, 5 April 2021

2021-04-05T07:40:36Z

← Older revision		Revision as of 07:40, 5 April 2021
Line 8:		Line 8:
	'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly hidden on purpose. It is important to note they still exist even if they are hidden. There are a few ways a trackfile is displayed:		'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly hidden on purpose. It is important to note they still exist even if they are hidden. There are a few ways a trackfile is displayed:

	If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (seen by the Radar). ~~This~~ feature can ~~also~~ be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but ~~rather~~ the display on the Attack format.		If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (i.e. seen by the Radar). Without this feature there would be no way to indicate the existence of Datalink-only trackfiles on the RWS Attack format. It can be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but just the display on the Attack format in RWS.

	'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.		'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.
Line 14:		Line 14:
	'''SA format.''' The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.		'''SA format.''' The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.

	'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button.		'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button. Both the L&S and DT2 positions are superimposed on the HUD and HMD; the L&S is a box and the DT2 is an "X" shape.

	'''Designation methods.''' To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.		'''Designation methods.''' To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.

Jak at 06:26, 5 April 2021

2021-04-05T06:26:30Z

← Older revision		Revision as of 06:26, 5 April 2021
Line 6:		Line 6:
	'''Scan volume/centering.''' The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.		'''Scan volume/centering.''' The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.

	'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly ~~not displayed~~. There are a few ways a trackfile is displayed:		'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly hidden on purpose. It is important to note they still exist even if they are hidden. There are a few ways a trackfile is displayed:

	If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (seen by the Radar). This feature can also be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but rather the display on the Attack format.		If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (seen by the Radar). This feature can also be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but rather the display on the Attack format.

Jak at 06:25, 5 April 2021

2021-04-05T06:25:53Z

← Older revision		Revision as of 06:25, 5 April 2021
Line 11:		Line 11:

	'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.		'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.

			'''SA format.''' The Situation Awareness (SA) format also displays all MSI tracks like the Az/El, but in a "god's eye" view. Unlike the Attack format, however, the SA display is just like the HSI format in that it is a 360° view around the aircraft, not a warped B-scope view like the Attack and Az/El formats which cover only 140° ahead.

	'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button.		'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button.

Jak at 06:23, 5 April 2021

2021-04-05T06:23:33Z

← Older revision		Revision as of 06:23, 5 April 2021
Line 2:		Line 2:
	The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.		The following is a summary of operating the A/A Radar in a generic engagement. It is intended to give a generalized description of functions and modes to better understand using the overall system, which is detailed in depth in the other sections.

	In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).		'''Range While Search (RWS).''' In the search phase of an engagement, the pilot generally desires to surveil a large chunk of space to detect targets for an attack. The Range While Search (RWS) mode is optimized for this purpose. An unlimited scan volume is available (as large as 6 elevation bars / 140° azimuth).

	The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.		'''Scan volume/centering.''' The size of the scan volume is changed on the Attack format using the azimuth width and elevation bar controls at PB20 and PB6. These options can be selected by pushbutton or via the cursor. The scan volume azimuth center can be easily changed on either the Attack or Az/El formats using the cursor. A quick TDC depress sets the scan center. The elevation can be centered in two ways: by using the Antenna Elevation wheel on the throttle or by using the cursor on the Az/El format.

	In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly not displayed. There are a few ways a trackfile is displayed:		'''Hits/trackfiles in RWS.''' In RWS, the Attack format provides a mostly decluttered view of raw hits, displayed as green bricks. However, RWS also processes Radar trackfiles like TWS, though they are mostly not displayed. There are a few ways a trackfile is displayed:

	If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (seen by the Radar). This feature can also be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but rather the display on the Attack format.		If designated, a trackfile will always be displayed as a HAFU symbol, with its Mach number and altitude to the left/right. In the case of a Radar track it is displayed ontop of the corresponding hits. Also, any trackfile can be displayed when the cursor is put over its corresponding raw hits. This is the Latent TWS (LTWS) function and can be toggled under the DATA sublevel if desired. With LTWS deselected, cursoring over a raw Radar hit will not display a trackfile, but will display the raw hit's altitude to the right of the cursor. Also, any trackfile in RWS with Datalink contribution is always displayed on the Attack format. This is regardless of whether it also has Radar contribution (seen by the Radar). This feature can also be toggled under the DATA sublevel at the "MSI" option. Note that neither the LTWS nor MSI selections have any effect on trackfile processing, but rather the display on the Attack format.

	On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.		'''Az/El format.''' On the Az/El format the pilot is provided a forward-looking projection of trackfiles. No raw hits are displayed and the Az/El format is not subject to the complex RWS display logic on the Attack format; rather, all tracks are always displayed regardless of Radar mode.

	The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button.		'''Designated trackfiles.''' The pilot is able to designate any Radar trackfile. The primary designated track is the Launch & Steering target (L&S). If desired a Secondary Designated Target (DT2) can also be made. The L&S points weapons to that target and also shows weapon launch parameter on the HUD and Attack format. The DT2 is simply used to monitor another track more closely as it also displays launch zones. The DT2 and L&S can be quickly switched with the Undesignate button.

	To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. The second way is with the cursor. ~~While it is~~ over any trackfile, depressing the TDC will make it the L&S, if none exists. If an L&S does exist, the track is instead made the DT2.		'''Designation methods.''' To actually designate trackfiles, two methods are available. The quickest way is by pressing the Undesignate button, which assigns the L&S designation to the rank 1 trackfile. Subsequent quick presses step the L&S designation through each trackfile. If the button isn't pressed for more than 4 seconds then the next press reassigns the L&S to the rank 1 track. Note that when a DT2 exists the Undesignate button cannot do this function as it swaps the L&S/DT2 instead. For this reason, it can be detrimental to have a DT2 if engaging three or more targets at once. The second way of designating trackfiles is with the cursor. When placed over any trackfile, depressing the TDC will make it the L&S if none exists. If an L&S does exist ready, the track is instead made the DT2. The DT2 itself can be designated with the cursor to make it the L&S and undesignate the old L&S.

	The other mode primarily intended for surveillance is Velocity Search (VS). VS does not create trackfiles ~~and~~ presents hits in a special azimuth over closure rage format. The advantage over VS is it realizes the maximum possible detection range of the Radar at the cost of poor target data (no range, therefore no altitude calculation, etc).		'''Velocity Search (VS)'''. The other Radar mode primarily intended for surveillance is Velocity Search (VS). A major disadvantage is the that VS does not create trackfiles. It presents hits in a special azimuth over closure rage format. The advantage over VS is it realizes the maximum possible detection range of the Radar at the cost of poor target data (no range, therefore no altitude calculation, etc). Outside this advantage, RWS is far preferred to VS due to its trackfile processing.

	Once the target or targets of an attack are detected and identified, it is usually desired to more closely track them. This is generally done by way of the Track While Scan (TWS) or Single Target Track (STT) modes. TWS can be entered via the mode option at PB5 using the pushbutton or via cursor. STT can be entered from RWS or TWS in a few ways, all termed methods of "acquisition". The most common method is Fast Acquisition whereby the desired trackfile or hit is placed under the cursor and the Sensor Control switch is bumped toward the Attack format. This also works on the Az/El format.		'''Entering Track While Scan (TWS) and Single Target Track (STT).''' Once the target or targets of an attack are detected and identified, it is usually desired to more closely track them. This is generally done by way of the Track While Scan (TWS) or Single Target Track (STT) modes. The transition is smooth since trackfiles are already being made in RWS. TWS can be entered via the mode option at PB5 using the pushbutton or via cursor. STT can be entered from RWS or TWS in a few ways, all termed methods of "acquisition". The most common method is Fast Acquisition whereby the desired trackfile or hit is placed under the cursor and the Sensor Control switch is bumped toward the Attack format. This also works on the Az/El format.

	In TWS mode, the scan volume is limited to maintain a scan frame time of 3 seconds or less~~, resulting~~ in a high trackfile refresh rate. Note that there is no difference in trackfile processing between RWS and TWS, but TWS provides better tools for ~~attack~~. In TWS, hits can be displayed like in RWS, but all trackfile HAFU symbols are also always displayed. Unlike RWS, raw hits can be removed in TWS ~~using~~ the HITS option at PB8.		'''Track While Scan (TWS).''' In TWS mode, the scan volume is limited to maintain a scan frame time of 3 seconds or less which results in a high trackfile refresh rate. Note that there is no difference in trackfile processing between RWS and TWS, but TWS simply provides better tools for attacking targets. In TWS, raw hits can be displayed like in RWS, but all trackfile HAFU symbols are also always displayed. Unlike RWS, raw hits can be removed in TWS by unboxing the HITS option at PB8. This makes the display less cluttered.

	One TWS tool is AUTO scan centering, ~~where~~ the L&S and DT2 trackfiles ~~are automatically maintained~~ in the scan volume. ~~The~~ pilot retains the ability to "bias" the scan volume as desired while maintaining the L&S/DT2~~, or use~~ MAN scan centering. TWS first defaults to MAN if entered from RWS or VS. AUTO is default when entering TWS from STT. A toggle is available at PB13.		'''TWS scan centering.''' One highly important TWS tool is AUTO scan centering, which automatically adjusts the Radar scan center to keep the L&S and DT2 trackfiles in the scan volume. In AUTO, the pilot retains the ability to "bias" the scan volume as desired while maintaining the L&S/DT2. This biasing is accomplished using the cursor just like in manual centering. Fully manual (MAN) scan centering is also available in TWS which functions just like in RWS. TWS first defaults to MAN if entered from RWS or VS. AUTO is default when entering TWS from STT. An AUTO/MAN toggle is available at PB13.

	STT is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, especially important for weapon guidance, at the cost of the Radar not scanning any volume of space at all.		'''Single Target Track (STT).''' STT operation is highly straightforward. The Radar is fully dedicated to tracking a single target. This results in the highest trackfile quality, especially important for weapon guidance, at the cost of the Radar not scanning any volume of space at all. The STT RAID mode is available for toggle via the RAID switch on the throttle. In RAID the Radar alternates between full track and brief scans where it searches for additional targets in a narrow vicinity of the STT target. A zoomed in 5nm x 5nm display is provided in RAID.

	The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular waveform. This guidance requires STT so the Sparrow can only be ~~employed~~ at one target at once and only in STT. The AMRAAM uses datalink ~~guidance~~ from the Radar for the majority of the ~~missile's~~ flight to the he target, which can be supplied in RWS, TWS, or STT. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. ~~Note that an~~ AMRAAM launch from RWS automatically commands TWS, but RWS could be reselected if ultimately desired.		'''Exiting STT.''' Return to Search (RTS) from STT can be done by pressing the Undesignate button. The Radar returns to TWS if STT was entered from TWS or RWS if it was entered from RWS or VS. The Radar doesn't return to VS since this would delete the existing trackfile. The Radar also returns to TWS regardless if an AMRAAM is in flight. The mode that will be commanded is indicated at PB5 under the word "RTS". There is also a TWS option at PB10 to go to TWS directly from STT.

			'''AMRAAM and Sparrow missiles.''' The main beyond visual range weapons available are the AIM-7 Sparrow and AIM-120 AMRAAM missiles which are highly integrated with the Radar. The AIM-7 uses pulse Doppler illumination (PDI) guidance, where the Radar physically "paints" a target with a particular illuminating waveform picked up by the Sparrow seeker. This guidance requires STT, so the Sparrow can only be guided at one target at once, and only in STT. The AMRAAM uses one-way datalink transmissions from the Radar for the majority of the its flight to the target, which can be supplied in RWS, TWS, or STT. This means the AMRAAM can be employed at many targets simultaneously. RWS is usually not used for AMRAAM guidance due to the previously mentioned advantages of TWS or STT, but it remains available. An AMRAAM launch from RWS automatically commands TWS, but RWS could be reselected if ultimately desired. Also, if STT is entered from RWS and an AMRAAM is fired, the Return to Search (RTS) mode becomes TWS, even though STT was entered from RWS.

	HAFU SYMBOLOGY		HAFU SYMBOLOGY