CAC/STT IFF

[IvanK]

Unless I have completely stuffed up when you lock using any of the CAC modes be it it radar or EOS you dont get the IFF ID on the Head Down (Radar) display. So how do you know if its friend or foe ? There is a means to get an ID for G15 users.

 

This G15 utility available here:

 

http://www.vjg71.de/index.php/Downloads/Lock-On/View-category.html

 

 

Gives you an unambiguous Friend or foe Ident in the G15 LCD regardless of method used to lock the bandit. Only problem is those On line servers that dont permit LUA export.

 

Great for those Close in Pop up targets you SCHELM or CAC acquire.

 

This works for the F15 as well.

[Cosmonaut]

That's a tough one. In CAC modes for RU Fighters you get an IFF ID in the HUD, if you're radar is switched on, but the HDD doesn't give you that info so you can't export the ID to your G15. Unless the HUD info can be exported?

 

Hehe you weren't asking just informing sorry..

Edited October 19, 2008 by Cosmonaut

[IvanK]

I see an ID in the HUD in TWS or Scan but never in STT or post lock in a CAC mode. What ID in the HUD do you get following say a Boresight lock on ?

 

However with this utility running on the G15 even with radar off and you get say an IRST CAC lock you always get the ID in the G15 LCD. it works beautifully.

[Cosmonaut]

Maybe I've misunderstood but notice the F (Cyrillic C if you have Russian HUD like me) that tells you its Friend not Foe.

 

 

 

Also double lines on the contact in STT is Friend.

 

Edited October 19, 2008 by Cosmonaut

[104th_Crunch]

Also see this thread for full IFF info.

[IvanK]

Ok thanks for the link and jpgs gents, I missed the "F" in the HUD in the Docs. However that still requires you to illuminate the target with Radar energy to get the ID ... and in a Track dose :) ... kind of eliminates surprise even though it might just be a short burst. Also requires another switch action.

 

With the G15 Utility you can do the whole thing with the Radar off. You take say a SHLEM loc just on EOS, the G15 Utility still gives you an ID everytime.

 

No problems understanding the HDD ID or the scan and TWS ID.

Edited October 19, 2008 by IvanK

[Kuky]

But that is not realistic then IvanK as actual system (EOS) cannot give you ID and IFF

[golfsierra2]

Kuky is right. IFF is an active system and can not be triggered by EOS / IRST.

The fact that the IFF readout can be displayed on a G15 display is a workaround using the game data and is not realistic in any way.

 

One could consider it a cheat.

Edited October 19, 2008 by golfsierra2

[Cosmonaut]

LUA exported IFF to G15, via EOS isn't realistic. :doh: lol

 

Although servers not allowing lua exports will make this redundant but if you're looking for realism then only use this for the F15 when in CAC mode.

[IvanK]

I agree on the realism ref EOS and ID bit, now I know about the "F" its not as critical.

 

Then again as I understand (western) Airborne interrogators the current mechanisation of LockOn is not realistic either. In LockOn with the radar on you have full time Interrogation going on in TWS or Search. Real World (as I understand it) requires pilot action (momentary switcholgy) to get the interrogator to operate.

 

Data Link ID is of course a separate issue.

Edited October 19, 2008 by IvanK

[nscode]

Actually, I'm not so sure that the radar must be in full blown active mode for the interrogator to work.

[Brit_Radar_Dude]

Real World (as I understand it) requires pilot action (momentary switcholgy) to get the interrogator to operate.

My background is Ground based radars, neverthless two things spring to mind as possibilities in airborne systems.

 

1) With the newer LPI aircraft radars, using continuous IFF interrogations would defeat the object of having an LPI radar as the enemy could easily detect your IFF interrogations.

 

2)In a real war, the first thing that any pilot would do is switch off his transponder from replying to Mode 1,2,3 or C interrogations, as any interrogator (friendly, enemy or civilian) can get his transponder to reply. He would only allow replies to Mode 4.

Consequently, the continuous use of mode 1,2,3,C interrogations would be pointless (no friendlies would reply) and may give away your position.

 

Much more likely is that pilot action is required to trigger a Mode 4 interrogation. Mode 4 is a very old (1950's technology) encrypted system, with codes that are changed each day. But as with all encrypted systems, the more data the enemy have to work with, the easier it is to crack the code for the day. Therefore you are cautious with generating interrogations, thus continuous Mode 4 interrogation is frowned upon.

[IvanK]

Good info Brit Radar Dude. I presume that what we are simulating in Lock On is the Russian equiv of Mode 4. Therfore requiring the airborne interrogator to ask for the response.

[golfsierra2]

Much more likely is that pilot action is required to trigger a Mode 4 interrogation. Mode 4 is a very old (1950's technology) encrypted system, with codes that are changed each day. But as with all encrypted systems, the more data the enemy have to work with, the easier it is to crack the code for the day. Therefore you are cautious with generating interrogations, thus continuous Mode 4 interrogation is frowned upon.

 

Much much more likely is that an enemy simply would jam both IFF frequencies and the whole electronic ID will go down the drain. Why waste time with decrypting key code tables ?