Yeah TGP does not want to lock helis. Embarassingly died to an MI-28s chin gunner…
Trying to lock it up.
God I want MFD slew controls so bad. Would be peak combined with this if added.
1 Like
But the Typhoon doesnt have sensor fusion :P
/s
Might be a shot to lock with the IRST and use the auto slew to just work off that.
1 Like
Im now just guiding manually when it comes to Helis they are usually arrogantly hovering.
That or the gun
that MFD picture seems to be taken from an EF with the AESA looking at the gimbal on the RWR screen
…interesting
the EF is at 10° azimuth and from 270° to 10° it is 100° of radar gimbal
7 Likes
Another interesting point is that the DASS format isnt displaying the current radar elevation coverage compared to its max elevation despite showing all other info the DASS format typically displays, potentially suggesting the radar has full elevation coverage
DASS format, elevation coverage shown on the right:
1 Like
like you mean it just automatically sweeps all 120° in elevation at all times? not surprised really, feel like all ESA’s should have this ability considering their ridiculous scan speeds
Also, when the DASS system, specifically the RWR section, detects a friendly unit, a green circle should appear, just like on the radar MFD, since they share the same symbology.
Spoiler
In the picture, the green circle represents a friendly, and the two red circles represent hostiles
Spoiler
3 Likes
Would actually be ±100deg, so 200deg of sweep in elevation, but yeah. If thats the case, the scan area would be 40000deg^2. In hindsight, it actually makes a lot of sense as well when you consider the that atleast one of the ECRS (i think the ECRS mk.2?) is mounted on a swashplate, which means that to scan the full 200deg of azimuth, the swashplate needs to do a full revolution anyways, so it might as well scan the whole elevation while its at it as well while its at it.
Scan speed isnt really what makes this functional imo, the ability of ESA radars, particularly AESA radars, to multitask by dedicating specific groups of T/R modules to individual tasks means that It doesn’t really matter if it takes longer to scan the full gimbal of the radar, as once a target has been scanned, it can be kept updated until it leaves the radar limits.
Its one of the reasons why I’m adamant in pointing out that one of the most important feature, particularly for ESA’s in WT, is their scan area, because the speed of the scan is largely irrelevant.
Edit: Scan speed is very important to make it functional actually. At 40000 deg^2 of scan area with the ~1176deg^2/s volumetric scan rate I had assumed for the CAPTOR-E based on an old source (regarding the early AESA radar for the EFT vs the CAPTOR-M), it would take 34s to complete 1 scan, so either the radar scans a LOT faster, or it doesn’t scan the entirety of its gimbal limits.
Wait Its Mk2 only? I thought it was also Mk1
just checked, the Mk1 also has a swashplate, unfortunately I also found out it has a slightly smaller scan area at ±90deg, so germany appears to be shooting itself in the foot, again…
ECRS Mk.1 details:
muhahaha :P
Though arent they looking to get a few mk2s for some of their EFTs?
Though knowing Gaijin. They are more likely to just model Mk2 to be identical to Mk1 (or even 1+2 to be identical to mk0) and not model the differences
I think theres some discussions going on about making it the radar for the EFT EK, but idk if its been decided yet.
Knowing gaijin they’ll model them to be the same except in gimbal limits, so the mk1 will be a strict downgrade.
Modelling aside, I genuinly have no idea wtf germany is doing with that radar. TheECRS mk2’s swashplate is derived from the ES-05 Ravens swashplate, and literally all documentation ive ever seen about any ?EFT AESA has ±100deg coverage, then the germans come in, reinvent the wheel, and give it ±90deg for some reason
STAP?
nose cone confliction maybe? Perhaps the Mk2 eliminated the problem
They may, but i guess we’ll have to wait and see. First things first. We need to wait for them to add CAPTOR-E. If they ever do
Space time adaptive processing: Radartutorial
No, cuz the Mk0 has the same coverage as the mk2, so the mk1 is just the special shortbus kid of the family I guess
The only thing I can think of is maybe the number quoted for the Mk1 is only the zone with max output, and the zone for the mk0 and mk2 is the technical limits, since the scan range beyond 90deg for those is reduced:
Eh, atleast for WT our will be better as we dont overload us with Informations )))))
2 Likes
Hu…
Well…
GG Germany… GG
smug “Those poor brits and their… checks notes …better scan angles and superior situational awareness…” xD
Realistically, I think the most likely thing is where the numbers mentioned for the ECRS mk0/2 are of a different standard than those for the ECRS mk1, since the mk0/2 are made by BEA and the mk1 by airbus germany. But if thats the case, the germans have shot us in the foot regardless by stating ±90deg instead of the ±100deg of every other eurofighter AESA has stated, cuz thats the number gaijin will go with.
The ES-05 is tripping me up even more, cuz their graph has 90deg on it for whats clearly 100 deg…
4 Likes