4.34 - IFF documentation
-
Below are 2 articles focused on IFF implementation in 4.34.
The pilot’s guide to IFF is meant for the average user : a quick user guide on how to interact with the system in the jet.
For the record, this was written before the Dash-1 section and is a bit rough around the edges. The Dash-1 is more complete and can be found here.
The planner’s guide to IFF is more technical. It is meant for TE/campaign/theater creators, so as to :
- tweak the mode/code generation process in the ATO.
- enable/disable IFF capabilities for each aircraft in the theater
Happy reading
EDIT : something not (yet) mentionned in the docs :
- every IFF interrogation and reply might be intercepted by the enemy.
That can be by an enemy ground station - anything with a radar - or ELINT flights. It depends on the emitting aircraft altitude and ELINT item position. That will make the emitting aircraft spotted for a while. Be aware of this, whether on the transponder side (dont blast every mode all the time, especially in a NOE penetration), or the interrogator side (dont interrogate in SCAN every second if you want your teammates to stay discreet).
- there can be errors in the transmission, known as ‘code garble’.
It happens especially at a distance or if multiple transponders are close together. That can result in a different code being perceived by the interrogator, a ‘unknown’ M4 reply, or no reply at all being seen. M4 is less prone to that. But it can be good practice to deactivate M1/M2/M3 when flying close together. -
Good job m8.
-
Thank You
Cheers
-
Below are 2 articles focused on IFF implementation in 4.34.
…
@Cruz: IMO it should be placed in Articles/Avionics section as well: https://www.benchmarksims.org/forum/content.php?116-Avionics
-
Great stuff Cruz! :thumb:
-
@Cruz: IMO it should be placed in Articles/Avionics section as well: https://www.benchmarksims.org/forum/content.php?116-Avionics
Agreed
-
Something is wrong with one section of the new IFF Section in Dash-1.
I added a picture with several boxes around the missleading descriptions in two colours. Red is for the Mode and Blue is for the Code. I think it is easily understandable, whats wrong.
Apart from this little mistake above, which I think does not disturb anyone:
Thank you Guys soooooo sooooo much. I dont have words for this incredible masterpiece you brought to us for free. Thanks!!!
Edit RD [Fixed]
-
Indeed, that example should always talk about Mode 1. Nice find
-
nice one. THANKS
-
And it could be pinned. Brilliant doc, clear and straight to the point, thank you!
-
Hello L3 ! Nice work !
Would you mind if i tried to translate it into french for our Folks on C6 ? -
Hello L3 ! Nice work !
Would you mind if i tried to translate it into french for our Folks on C6 ?Sure, go ahead ! I’ll be reading the result
-
:munch::munch:
-
Sure, go ahead ! I’ll be reading the result
Thanks ! I will send it to you to check it up before releasing it
-
Added a few more infos, missing from the docs, in the first post.
-
Can someone make a tutorial with iff concept as a whole in youtube ? Its tough especially with events depending in time and pos
-
There is already a topic for that (but i can’t find it anymore)
Anyway :
->
-
I have seen that i cannot understand the half of what he sais lol someone with native english would be better
Or any greek could make a video with iff?
-
-
After some fiddling with the .iff files, I discovered it can be a bit annoying to have to calculate the sum of the binary values of all modes you want to activate, so I made this very simple Excel-file to do the work for me. Other mission makers may find it useful too.
And while I am here, I’d also like to inform you that M1 is not limited to 2 digits anymore. If the proper equipment is installed on the aircraft, it can be 4 digits as well. (BUP will then set the first 2 digits)
Would be nice if this could be looked into, and added in a future (not necessarily the next ) update.