AESA Radar range calculator.

Member for

4 years 1 month

Posts: 905

Greetings. It's been a while since i post a thing here.. bit boggled with some IRL issues. But well here i come. So what i shared is, kinda small project of mine based on my interest toward radar. The AESA Radar range calculator here is an excel spreadsheet, made based on several books like SKolnik's 3rd Introduction to Radar system, Stimson's 2nd Edition of Introduction Airborne Radar and others. The calculator will attempt to predict radar ranges based on inputted variables and taking account of some important things that for some reason not considered by other calculators like pulse integration, scan sectors and most importantly the antenna weighting scheme. As we know AESA Radar or perhaps even its Hybrid Array sibling like N011M Bars is capable of actually altering its radiation pattern, based on algorithms like Taylor, Cos, Hamming. etc. Even special algorithm has been developed for AESA. The change in radiation pattern allows reduction in sidelobe, beamwidth optimizations, or even total split of the aperture into several smaller one for search. In cost of efficiency and angular resolution. This calculator however are still what you call as "Noise limited", basically it's not taking account things like ground clutter or weather. However i think for case like high altitude combat, it's good. It has simple interface and i believe quite easy to understand. [ATTACH=JSON]{"alt":"Click image for larger version Name:\tesa_feature_by_stealthflanker-db04d9s.png Views:\t1 Size:\t116.2 KB ID:\t3731792","data-align":"none","data-attachmentid":"3731792","data-size":"custom"}[/ATTACH] The download link. https://www.mediafire.com/file/fdmzssya84htnck/AESACalcStable-ReleaseVer.xlsx/file?fbclid=IwAR3VncbImKtFdunpPY094sjBnP-iy_pgBzzM-YMQ0Hzos7wpjUua-yFJzQg critics and suggestion are welcome.
Attachment Size
esa_feature_by_stealthflanker-db04d9s.png 116.16 KB
Original post

Member for

3 years 9 months

Posts: 1,081

Very detail , i love it.
Profile picture for user MSphere

Member for

9 years 7 months

Posts: 8,850

Great work.. congrats.. far more advanced and detailed that I could ever have gathered together.. one thing if I might ask.. is it possible to upgrade a radar with an antenna of a certain aperture and certain amount of elements by replacing the antenna with a different one with larger TRM count? Say your APG-77 has 2,000 TRMs, today, could it get a 2,700-TRM array one day? I am quite sure that the R&D and technology enable to pack the TRMs into tighter space, but ain't the physical dimensions of the emitter/receiver limited/dictated by the respective radar band? thanks

Member for

3 years 9 months

Posts: 1,081

AFAIK, Too narrow spacing between T/R modules may cause the system to have bad overheat or mutual coupling

Member for

15 years 9 months

Posts: 114

Looks great. What are the parameters which control beamwidth? I always taught about a AESA that concentrates the RF energy via resonance and hence achieves greater ranges. At some point the amount of airspace electronically scanned would increase the time for a complete scan of the hemisphere too much. But for specialized purposes such as target illumination, could the beamwidth be significantly improved compared to a PESA? Thanks.

Member for

4 years 1 month

Posts: 905

Looks great. What are the parameters which control beamwidth? I always taught about a AESA that concentrates the RF energy via resonance and hence achieves greater ranges. At some point the amount of airspace electronically scanned would increase the time for a complete scan of the hemisphere too much. But for specialized purposes such as target illumination, could the beamwidth be significantly improved compared to a PESA? Thanks.
The beamwidth of the AESA is directly controlled by the number of its elements, which govern the physical dimension of the antenna. Weighting algorithm can later be introduced to control radiation pattern. However one cannot really make beam narrower unless the antenna is enlarged. In the calculator the basic equation to calculate beamwidth is : [ATTACH=CONFIG]252020[/ATTACH] The resulting beamwidth is later multiplied by the "Beamwidth factor" or "K" from the tapering algorithm drop down menu.
Great work.. congrats.. far more advanced and detailed that I could ever have gathered together. one thing if I might ask.. is it possible to upgrade a radar with an antenna of a certain aperture and certain amount of elements by replacing the antenna with a different one with larger TRM count? Say your APG-77 has 2,000 TRMs, today, could it get a 2,700-TRM array one day? I am quite sure that the R&D and technology enable to pack the TRMs into tighter space, but ain't the physical dimensions of the emitter/receiver limited/dictated by the respective radar band? thanks
Apparently that's the plan for US AMDR Radar, where they have some sort of "common module" block. So what you need to "upgrade" is Physical space. For fighter radar tho, i am not so sure as the space and power generation there is very premium. There is of course another consideration of using less modules than what an antenna can actually accommodate like cost or RCS reduction, from edge treatment. Other possible consideration is cost as we know TR module is still an expensive item. Cost issue become critical if you desire to use higher frequency (say 94 Ghz AESA) and wish for a full array. you would need thousands of modules. Anyway related to cost, i included a small chart depicting several factor and their relations to wavelength. As you see cost increase exponentially when you move to higher frequency (shorter wavelength) The size of the AESA T-R module is governed by physics. The width is the primary dimension, where it need to be about half wavelength. So for X-band the module's width would be about 1.5 cm for 3 cm operational wavelength. Technology can only goes as far as packaging, cooling and materials.
Very detail , i love it.
Thanks a lot. :D

Member for

4 years 1 month

Posts: 905

Updates Slight updates to the calculator. The Required SNR variable is now automatically calculated by the spreadsheet. The Calculated SNR is for Swerling 1 or 2 target. Representative for maneuvering fighter aircraft, and basically the goal of any fighter/tracking radar designer (as making the target behaves in swerling 2 will reduce the required SNR) As you see no more SNR variable. [ATTACH=CONFIG]255484[/ATTACH] Instead it's become part of the calculated variable. The calculated SNR is for 90% probability of target detection. Which allows lock on. Thus the R90 in the bold coloumn is the range where target could be locked on by the radar and later fired upon by the radar platform. [ATTACH=CONFIG]255485[/ATTACH] The range coloumn [ATTACH=CONFIG]255486[/ATTACH] The R50% is the range where target detection probability is 50%. Such range is where radar might detect and track the target But not having the confidence of locking it for weapon system employment. It may however be used to cue other fighter aircraft or higher resolution sensors to establish more confidence on what being detected, is it real target or just false alarm.

Member for

7 years 4 months

Posts: 998

So many variables iam overwhelmed with choices.

Member for

4 years 1 month

Posts: 905

what do you mean @moonlight ?

Member for

13 years 6 months

Posts: 1,009

for laymen it would be easier if there were just several choices, and everything else was approximated (average and/or generic values used), even if it meant significantly greater errors. Anything other than these variable might confuse most people: output power, antenna diameter, target RCS, wavelength.

Member for

4 years 1 month

Posts: 905

@totoro Thanks for the input. Let's see what i could do. Using approximations is good however the calculators may lost its flexibility. and some variables like PRF can't really be "automated" unless locking the calculator in specific frequency (say X-band) But we will see.

Member for

4 years 1 month

Posts: 905

Improvements time. Trimming down some variables and Provide pre-calculated one. The calculator basically remains the same BUT hopefully it's more user friendly. [ATTACH=CONFIG]255520[/ATTACH] The cover page now feature less clutters and lesser amount of input. Unfortunately as i said previously, pulsewidth and PRF cannot really be "automated" as it depends on the radar mode. Eliminating them will essentially locks the functionality of the calculator to X-band. While we know Russian developed L-band leading edge radar. and we have AEW AESA radar such as APY-9 and Elta Phalcon. For filling guide for PRF and pulsewidth however. One can consult to following table, genereously provided by Carlo Kopp in Radar Handbook 3rd Edition. For both A2A and A2G modes A2A https://orig12.deviantart.net/f8ac/f/2017/186/0/6/radar_a2a_by_stealthflanker-dbf5rk5.png A2G https://orig11.deviantart.net/f5ed/f/2017/186/5/1/radar_atg_modes_by_stealthflanker-dbf5rk2.png The second page of the calculator contains the pre calculated variables. One may still edit them. However it could be left as is. The pre calculated variables are based on generic information provided by radar literature in my possession. [ATTACH=CONFIG]255521[/ATTACH] Hopefully it could be more useful and easier to use. However feedback and input are appreciated. Download link for the Improved version : https://www.mediafire.com/file/7wrkyslc1p4d36r/AESACalcTrial.xlsx

Member for

10 years 7 months

Posts: 394

is it possible to upgrade a radar with an antenna of a certain aperture and certain amount of elements by replacing the antenna with a different one with larger TRM count?
Unless the modules were larger than half wavelength for some weird reason, the answer is no. If you tried to space the modules closer than lambda/2, you'd end up with multiple beams going in different directions. Not very useful for a radar.

Member for

7 years 8 months

Posts: 4,165

VERY complicated, but certainly not impossible AFAIK, changing time shifts no? lambda/2 is linked to 60° value isn't it?

Member for

3 years 9 months

Posts: 1,081

If you tried to space the modules closer than lambda/2, you'd end up with multiple beams going in different directions. Not very useful for a radar
AFAIK, lambda/2 rule is for upper limit rather than lower limit. Lambda/2 spacing give the best gain though IMHO https://basicsaboutaerodynamicsandavionics.files.wordpress.com/2016/04/grating-lobes.png

Member for

4 years 1 month

Posts: 905

What gain ? Anyway Lambda/2 spacing from image above give scanning without grating lobes. Any other spacings be it less or more should have other consideration on choosing like say economy. The risk associated by using other form of spacing for ESA elements are limited steering angle. One example is ESA modules in TOR-M1 system which have wide spacing of lambda*3. The Russian designer opted such scheme for economy while providing best aperture area and gain possible. Whle accepting electronic steering angle of only 7 degrees. Other possible reason for choosing non half wavelength scheme is stealth as to reduce bragg lobes. Bragg lobes

Member for

7 years 4 months

Posts: 998

@stealthflanker: I mean there are too variables so i don't know what to choose to calculate range. For example: I want to estimate air to air range of radars like APG-77 and APG-81. But i have no idea what to put in Doppler filter per band or system loss budget. Even pulse width is hard for me to decide, especially with technology like pulse compression. Basically what said by totoro.

Member for

5 years 11 months

Posts: 2,012

I want to estimate air to air range of radars like APG-77 and APG-81
I gave it a shot: APG-81: T/R modules: 1626 Peak power per module: 10W Operational wavelength: 3 cm Aperture weighting: Taylor40D Radar PRF: 10 Khz, Pulse width: 20 micro sec => Duty cycle: 20 % Scan time frame: 9 seconds for full search volume. Scan volume: 20° azimuth, 10° elevation (Cued search => longer dwell time => longer range) Against target with RCS = 3m2 Maximum detection range with 50% probably of detection = 391 km Maximum detection range with 90% probably of detection = 242 km http://www.f-16.net/forum/download/file.php?id=25351&mode=view

Member for

15 years 9 months

Posts: 114

When I reduce the radar scan sector angles I would expect a rather proportional increase of detection range, but sometimes there is even an decrease. Is the aperture gain included in the spreadsheet so that there is a limit from which on no increased detection range can be achieved by confining the scan angles?

Member for

4 years 1 month

Posts: 905

The limit lies in the pulse integration loss. Not all of them can be integrated by the radar, and thus integration loss occurred. This in radar range equation will actually increase the required signal energy for target detection.

Member for

4 years 1 month

Posts: 905

It is update time and various other stuff. What's new : -Antenna type added https://sta.sh/024qp486qzs7 Allow range calculation for typical aircraft nose radar and linear array that might be embedded in your wing leading edge or vertical stabilizer. -Scan time now determined by dwell time. An advantages of AESA or general ESA radar is that the beam is controlled by computer and practically have no inertia, thus can be precisely controlled to achieve required dwell time/time on target. Dwell time is basically the time where radar beam will "stay" in a sector. It's a fraction of the total scan time (or time frame) or in fighter aircraft we know it as "scan cycle" This is typical fighter aircraft radar scan scheduling. As you see typical scan for fighter aircraft radar is about 1-5 seconds. Too long may cause problem in terms of update rate and tracking verification. In conventional mechanically scanned radar, this determined by the mechanical ability of the radar (actuator, hydraulics etc), which not much can be done with it. [ATTACH=CONFIG]255877[/ATTACH] In previous version user can input their scan time, which later the sheet will "allocate" it according to the scan area inputted by user. In this new version the scan time is now dependent on dwell time, which now made select-able in drop down menu by user. [ATTACH=CONFIG]255878[/ATTACH] The value in the drop down menu is based on Typical dwell time for Long range early warning radar, target acquisition and typical fighter radar found in table 1.8. ch1 from Lynch's "Introduction to RF Stealth" [ATTACH=CONFIG]255879[/ATTACH] Another additional function is atmospheric effects in shape of attenuation by atmosphere, and rain. [ATTACH=CONFIG]255880[/ATTACH] I would like to add snow, but there seems to be problem in interpolating available data, or more like it's kinda hard to do so due to nature of atmospheric absorption. However for typical radar frequency it appears to be quite satisfactory. The model used is based on simplified K.Barton's atmospheric attenuation model. There is more complete model by L.V Blake, but i decided not to use it for now to keep things simple. Another improvements and additions are the antenna weighting algorithm. adding new algorithms which you can try and have fun with. If anyone asks why Taylor is the default it's because Taylor weighting is the easiest to implement and quite robust. [ATTACH=CONFIG]255881[/ATTACH] Below the weightings there are new tables detailing antenna parameters for Linear and planar array. They're there to help calculating range in the next worksheet. The assumption for the linear array however is as follows : 1.Microstrip patch, with aggressive tapering in elevation beamwidth, original beamwidth was 114 degrees. However with proper lens treatment it can be reduced to the value you see in the table. 2.The spacing would still be half wavelength thus entire array length would be N*d where d is spacing in half wavelength. and beamwidth is Ka*(2/N) where N is number of elements and Ka is the weighting factor. The planar array is your typical nose radar. [ATTACH=CONFIG]255882[/ATTACH] Below the antenna table lies the dwell time selection table. This table lies the dwell time and will calculate the required scanning time based on the number of beam positions need to be scanned. In case you see changing the value of the scanning area increase the radar range, it's because the sheet will adjust the value of the scanning time to the new sector. You can edit the dwell time value to your fitting. The scan time however is off limit. Major change in Pre-calculated worksheet. Now most of it are automated Thus can't be edited. You can still however edit the value on green columns [ATTACH=CONFIG]255883[/ATTACH] System temperature now fully automated. [ATTACH=CONFIG]255884[/ATTACH] Loss budget, some of it are still editable, and the radar range gate and receiver columns too. [ATTACH=CONFIG]255885[/ATTACH] The fluctuation loss modeling. Now it's fully modeled. The target is assumed to be Swerling case-2 target. Suitable model for tracking radar and what radar designer want target behave to. Swerling case 1 could also be applied. However this model is more suitable for search radar, esp rotating search radar. [ATTACH=CONFIG]255887[/ATTACH] The new worksheet. The atmospheric effect, the most likely source of problem. This worksheet contain the "atmospheric model" and radar receiver noise figure "model" Based on excel trendline interpolation. The data is fortunately fits well so, the calculator is "work" However in the future i will implement better module. https://sta.sh/025kc3vsbsp8 https://sta.sh/0sz0c9zanfw As always feedback are appreciated. Download Link for updated version : https://www.mediafire.com/file/7wrkyslc1p4d36r/AESACalcTrial.xlsx