Incorrect threat library modeling for digital RWR

Within the framework of the game and the future update of “Firebird” digital RWR systems cannot identify some aircraft and ground radars, for example, Pantsir-S1, displaying the indication “AAA”, which is incorrect based on the sources that will be indicated later. Setting up a threat library, namely EID tables based on the RLE/RTE documentation and other technical documentation is not correct since it does not display the entire life cycle of aircraft equipped with digital RWR systems,I will base my work on a variety of sources representing scientific works in the field of EW technologies and RWR systems from both US military personnel and civilians, as well as brochures and proposals from defense companies. All links to sources will be provided at the end of the bug report.

Digital RWR systems use antenna receivers to detect threats, which receive a radar signal, after which the received radiation is analyzed by the onboard computer to identify characteristics that are then compared with the characteristics of known radars pre-loaded and located in EID tables. Tables that indicate the characteristics of known radars are called EID (hreat identification tables) and are part of the threat library (theart database), which in turn is part of the UDF / MDF / MD. UDF / MDF / MD files are a file that contains the necessary information for configuring aircraft systems, which is formed in the case of the US Air Force “53rd Electronic Warfare Group”. The MD file is then loaded into the aircraft’s avionics through various interfaces, such as RS-232.

Reprogramming of EID tables and consequently loading of new UDF/MDF/MD occurs according to the plan once a year or in the following cases: 1. If new threats have been detected by means of radio reconnaissance and their radar characteristics have been identified. 2. Shortcomings and errors in the operation of the RWR system have been detected in order to eliminate the problems. 3. At the user’s request in order to add/remove threat data from EID tables.

Sources:
ADA119252 (ALR-46 COMPUTER GRAPHICS SYSTEM FOR THE ROBINS AFB ELECTRONIC WARFARE DIVISION ENGINEERING BRANCH LABORATORY):
Page 15-16 (physical 2-3)
Threat file modification cases in AN/ALR-46.
Page 17-21 (physical 3-8)
Reprogramming the AN/ALR-46 threat library.
Pages 34-37 (physical 21-24)
Operation and threat identification principles and their characteristics by the AN/ALR-46 system.
ADA124712 (AUTOMATED TOOLS -FOR TEST AND ANALYLSIS OF RADAR WARNING RECEIVER SOFTWARE):
(Page 15 (physical 1)
Analysis of the term EID, the operating principle of digital RWRs and the difference from analog ones.
Page 16-17 (physical 2-3)
Analysis of the AN/ARL-46 system.
Page 17-18 (physical 3-4)
Reasons for changing data in RWRs and planned data changes.
ADA377365 - RTO-AG-300 Vol. 17 (Electronic Warfare Test and Evaluation):
Page 22-23 section 2.0 item
General information on the operating principle of RWR systems.
ADA566236 (ELECTRONIC WARFARE AND RADAR SYSTEMS ENGINEERING HANDBOOK):
Page 210-216 (5-8.1 and 5-8.7)
RWR Operation and Threat Identification Principles.
Page 332-338 (9-1.1 and 9-3.3)
RS-232 and RS-422 Data Interface.
Page 345 (9-6.1)
MIL-STD-1553 Data Interface.
ARCHIVED REPORT ALR-66(V)/606(V) - Archived 6/2004
Page 2-3
AN/ALR-66 Parameters and Specifications with Reprogrammability Confirmation.
DIGITAL SIGNAL PROCESSING FOR RADAR RECOGNITION IN DENSE RADAR ENVIRONMENTS by Hemant Kumar Mardia:
Page 113-133 (item 5.1)
Description of RWR system and threat identification principle.
Electronic Warfare Fundamentals NOVEMBER 2000 by Nick Numlk
Page 264-283 (17-1 and 17-20)
Description of RWR system and threat identification principle.
Page 271 (17-8)
Updating data in EID tables based on multiple factors.
ELECTRONIC WARFARE INTEGRATED REPROGRAMMING AND NOTIFICATION PROCEDURES:
Page 2 (item 1)
Analysis of the term PACER WARE.
Page 13 (item 7.3)
Information on RWR reprogramming.
AD1157188 ​​(MACHINE LEARNING APPLICATION FOR MISSION DATA REPROGRAMMING):
Page 11-14 (physical 1-4)
all about MDF, Definition of the term MD, tasks, development of MD, definition of tasks of the 53rd Electronic Warfare Group, terms of development and formation of MD.
Page 17-19 (physical 7-9)
The principle of operation of RWR on the example of AN/ALR-56 and the process of formation of MDF/MD.

Third party sources:
Bae systems website about RWR AN/ALR-56C indicating the ability to reprogram
EID tables after equipment delivery. quote “User programmability allowing system threat changes after delivery.”
Lockheed Martin website about RWR AN/APR-48B indicating the ability to reprogram the UDM file with threat library changes via RS 232-422 and MIL-STD-1553B interfaces in response to new threats or missions. quote "SYSTEM INTERFACE The AN/APR-48B system primarily operates on a dual-redundant MILSTD-1553B databus. Other commercial I/O interfaces including gigabit ethernet, RS-232 and RS-422 are available for future growth. The UDM can be rapidly reprogrammed with a new threat library, allowing system operation changes in response to new missions or threats.
Contract (Engineering Services in support of the AN/ALR-46/69 (new number FA8523-17-R-0002)) in which one of the clauses speaks about providing software support for updating the ALR-46/69 Operational Flight Programs (OFPs) and Emitter Identification Data (EID) tables.

Taking into account all of the above the above and the convention in which the aircraft can meet with opponents that it could not meet in a real battle, the correct solution would be to enter into the EID table all possible threats within the game, provided that they can be identified (they are not a radio range finder or other primitive radar) and the radar operates in the same frequency range as the RWR. I know about the limited number of threats that can be simultaneously recorded in the EID table, but within the game, such a number of threats cannot appear at the same time that would exceed the real limits.

I have links to sources, but unfortunately the forum has a limit on the number of links in the text (only two) absolutely all sources are declassified.
I am open to communication and ready to help in analyzing the information provided.

Well you have to use the bug report site:
https://community.gaijin.net/issues/p/warthunder

And your entire post is just about SPAA?
Since I see nothing about F-1C’s radar in your report, and that’s really the only age of air to air radars no longer identified.

This post was flagged by the community and is temporarily hidden.

So you got your answer already.
Why are you spamming it here then where it doesn’t belong when you already got rejected in the proper place?

1 Like

what is the answer? that no specifics were provided although I refer to real documents? wow that actually makes sense