HTS lags in detection behind ALR-56M - is this accurate?

[Istari6]

One thing my group has noticed is that there's often a significant lag in detection between when the RWR picks up a SAM threat, and when it displays on the HTS.  This has surprised us, since we figured the HTS is a specialized device for sniffing out and localizing ground threat emitters.  Yet we've had many situations where we're being locked up or even fired upon by a SAM, and nothing is showing on the HTS to respond against.

I know we can go direct to the HARM's HAS mode and fire back against threats that way, but it's certainly confusing how HTS is operating now.  Is this realistic?  Do we know if the real HTS has a lag in detection like this?  Or are there any other workaround to let the HTS "catch up" to the RWR faster? 

[Delta134]

The functioning of the HTS is described on page 285-287 of the manual. Delay between the RWR and HTS can be explained by the Scan Cycle Time. The Scan Cycle Time can be decreased by disabling Threat Classes on the HAD Threat Page as explained on page 292 of the manual.

Edited November 19, 2024 by _Delta13_

[Istari6]

Ah that makes sense.  I remember that being an issue with the HARM when used alone, didn't realize it also applied to the HTS.  Thanks for the answer!