Question on Sidewinder DLZ
-
I’m a little confused between sources on the Sidewinder DLZ. The legacy manual states:
The DLZ bracket only provides kinematic information on a potential missile shot. Kinematics refers to the ability of the missile to come off the rail and make it to the target not guide on the target just get to the target. Any shot between Rmax1 and Rmin1 can theoretically make it to the target. Shots between Rmax2 and Rmin2, however, have a higher probability of making it to a target that is maneuvering to avoid the missile.
I understand the principle, but the shape of the two brackets, left and right facing, confuses me. I assume RMAX 1 is at the top, then RMAX 2, then I’m confused as to whether RMIN 1 or RMIN 2 comes next.
I have AL and 5 above the DLZ. I’m not sure about AL but I believe 5 indicates the DLZ range.
I understand that closure rate is to the left of the carat.
F004.5 I understand is slant range to the target.
The RMAX and RMIN indications are what I mostly need to clarify as I think BMS has progressed somewhat through the documenation I’m looking at.
-
I’m a little confused between sources on the Sidewinder DLZ. The legacy manual states:
I understand the principle, but the shape of the two brackets, left and right facing, confuses me. I assume RMAX 1 is at the top, then RMAX 2, then I’m confused as to whether RMIN 1 or RMIN 2 comes next.
I have AL and 5 above the DLZ. I’m not sure about AL but I believe 5 indicates the DLZ range.
I understand that closure rate is to the left of the carat.
F004.5 I understand is slant range to the target.
The RMAX and RMIN indications are what I mostly need to clarify as I think BMS has progressed somewhat through the documenation I’m looking at.
You’ll see two staples; one inside the other. Starting from the top the order is: Rmax1, Rmax2, Rmin2, Rmin1.
-
This is one of those times when almost as soon as you write out the question you realise the answer.
The thing that’s puzzling me now is the TD box. I don’t see one with the HUD Scan, or “20”, ACM submode. It appears with the other submodes.
I’m assuming the TD box marks the highest priority target.
I’m ignoring the “Spot/Scan” options at OSB 3. I’m wondering if those are actually implemented.
-
Target Designator. The TD box is drawn around the STT target in most modes, as well as the GM and GMTT track. Its occluded by a few symbols, so its not always seen.
Spot and scan are sorta implemented, in that they do change the behavior of the seeker when its looking. In scan it nutates around a point, while in spot it looks directly at that point.
Pretty sure you wont get a TD box while searching in any ACM mode. Once it finds a target inside 10 miles it will go to STT and you should get a TD box. It should represent the radar target, not the highest priority.
-
I hadn’t thought about STT. I suppose with HUD Scan it might be I’m not seeing a TD box because I’m not allowing enough time for it to complete its scan. Though it does say “no rad”, which puzzles me.
I did read that Scan increases the FOV of the seeker, but I couldn’t detect an obvious difference.
I don’t think I’ve researched a topic on this so far that raised so many points of interest.
-
NO RAD is not radiating or no radar. ACM has five distinct direct submodes: 10x60, Slew, Bore, 30x20, and 30x20 Standby. The last one is the initial state when ACM is selected and the result of TMS aft in every state but itself (TMS aft in standby commands 10x60). 30x20 Standby will never find a target.
SCAN v BORE with AIM-9 produces the “dancing diamond” which increases the area which the AIM-9 can self-uncage (TD). Frankly I prefer bypass (BP) because I can’t stand not having control over uncaging (or really caging if I don’t want that target). I think it’s actually something BMS isn’t modeling 100%. With BP there’s no point in the scan since it needs my input to uncage and can’t do it automatically.
In most actual combat situations I slave the seeker via FCR which again renders SCAN irrelevant.
-
I hadn’t thought about STT. I suppose with HUD Scan it might be I’m not seeing a TD box because I’m not allowing enough time for it to complete its scan. Though it does say “no rad”, which puzzles me.
I did read that Scan increases the FOV of the seeker, but I couldn’t detect an obvious difference.
I don’t think I’ve researched a topic on this so far that raised so many points of interest.
If its searching, then you wont get a TD box, because at that point you dont have a target. As above, if it says NO RAD, then its not even searching, the radar is just not emitting at all.
The only symbology that should occlude the air to air TD box is the 50 mr gunnery reticule. I dont think that is relevant to the EEGS display, though, so basically the TD box should not be occluded unless it is outside the HUD FOV (in which case you get the pitot pointer, or TLL (Target Locator Line)).
-
Why would the radar not be emitting in HUD Scan submode? RF is set to Norm at all times and all the other submodes work fine. That’s the one thing I really don’t understand at this point.
I’m guessing that it’s set to standby on the control page? I will have to try that out later.
-
When you enter ACM, you immediately get NO RAD because thats how its programmed. You have to tell it what mode you want before it starts searching. Its not set to standby on the control page, its that the default ACM mode is standby. Where you go from that is up to you.
-
That explains it. You have to press TMS Right to make it active.
-
It’s not that 30x20 doesn’t radiate, when selected it does. There is just a non-radiating standby mode which happens to be labeled 30x20 as well. The ACM standby really didn’t need to carry the 30x20 label.
-
That explains it. You have to press TMS Right to make it active.
What happens if you push TMS Forward instead?
-
Oh my! Looks like TMS forward also makes the radar active!
I am shocked.
-
Entering dogfight mode is the hotas way to silence radar emissions.