[CORRECT AS IS] Problems with TWS, bad work.

[Padonis]

Case one

After selecting the TWS mode, the radar automatically locks on the target. It probably shouldn't be like that. In addition, I cannot remove the lock from the target. Pressing the "RESET" button does nothing. I need to go to RWS mode and remove the lock. After switching to TWS mode, the target is automatically locked again and the lock cannot be removed from the target.

 

 

Second case

I pass the target, activate the TWS mode and, oddly enough, the radar blocks the target behind me. I turn 180 degrees, the radar is still tracking the target that is missing and cannot be seen. Such situations often happen that the radar tracks the target in a place other than the radar shows.

 

 

I will try to post more such cases.

[Harker]

For the 1st case, IIRC, TWS always has an L&S target and pressing RESET will re-prioritize the trackfiles and default the L&S to the highest ranked trackfile. So that appears to work correctly.

 

For the 2nd case, TWS in the Hornet has known to do some weird stuff, but it could also be (in some cases, yours is a little too far fetched indeed) that the radar maintains a trackfile and extrapolates it, which means that until the radar realizes there's nothing there, the trackfile is just a point in space that moves based on extrapolating the motion of the target when it was last detected. I won't pretend to know the limitations of this systems and how it actually works though.

[Padonis]

In RWS mode I can lock the target (ENTER - TDC DEPRESS) and unlock at any time ("S" -Undesignate Target Rader Lock) change and block again. In TWS mode, this cannot be done anymore. I lock an inch automatically or manually (ENTER - TDC DEPRESS), but there are problems to remove the lock. Previously, this was done using the "RSET" function. Again, it was possible to set the goal on goal and to block the goal. In TWS mode "S" -Undesignate Target Rader Lock is used to move between tracked targets (L&S and DT 2).

If I block an ally, after selecting the RSET function, he hears that my lock on him has been removed. However, nothing changes on the radar displays, the target is still blocked. I have to turn my back on my target to remove the blockade and have power over the radar again.

If RSET returns only to L&S, then what is the complete deactivation of the lock, also L&S? In this film at exactly 30:42 minutes the film somehow did it. The L&S blockade has completely disappeared.

Edited May 25, 2020 by padonis

[Swift.]

I think the problem here is you are confusing the so called 'hard lock' of RWS/STT, with the 'soft lock' of TWS. When you have L&S cues in TWS, the target isn't 'locked' all that is happening is the computer is displaying the highest priority track file to you in the HUD.

[Harker]

Again, TWS will always have an L&S if it can. You can't force it to not have anything. And it's not a full STT lock, it's just a track, like Swiftwin9s says. In the video you show, he didn't do anything and he didn't lose the lock on purpose. TWS loses the L&S only if it can't maintain it for some reason.

[Padonis]

OK, gentlemen, I gave the problem, because before pressing the RSET button, the lock and L&S would turn off. In that case it had not been worked out before.

However, it remains a matter of how it is possible that the radar can block a target that is beyond the radar scanning range and still try to guide it. And also often can not block the target that is right in front of the pilot's nose, and once it blocks it easily loses it and extrapolates its position, even though the target is actually very close.

[Baikingu]

OK, gentlemen, I gave the problem, because before pressing the RSET button, the lock and L&S would turn off. In that case it had not been worked out before.

However, it remains a matter of how it is possible that the radar can block a target that is beyond the radar scanning range and still try to guide it. And also often can not block the target that is right in front of the pilot's nose, and once it blocks it easily loses it and extrapolates its position, even though the target is actually very close.

The range you set on your radar scope in the cockpit (lets say 40 [nm]) does not imply that the radar will only scan out to max 40 nm. The nr. 40 in the top right of the radar display only indicates the radar scope's current "zoom".

The radar it self will scan out to 180 nm and beyond. (All though you prob. won't get a radar return[contact] at 180+nm. hence the 180 max range "zoom")

 

 

As for up close you have to concider that the radar beam emitted from your radar is in a cone shape protruding out from the nose of your plane in a about a 3 or 5 degree angle (not quite sure of the degrees). See pic.

As you can tell the closer the target gets the more you/the radar has to scan up/down/side to side in relation to the target to keep it in the radar beam. (cone)

In STT the rader focuses in one target only and follows it automatically up/down/side to side with in the radar gimble limits to keep lock.

But in TWS you have to do this manualy if you don't put it in AUTO mode. Then the radar will center the scan zone on your L&S cue and follow it with in the radar gimble limits.

 

Note: TWS was not implemented in till late last year if I remeber correctly. Before that we only had LTWS which is essentially RWS just with the ability to see L&S then you hover the TDC over a radar contact. THis might explain why you could "unlock" with RESET before

Edited May 25, 2020 by Baikingu