Radar Tracking and Jamming

STK Premium (Air) or STK Enterprise
You can obtain the necessary licenses for this tutorial by contacting AGI Support at support@agi.com or 1-800-924-7244.

Required Capability Install: This lesson requires an additional capability installation for STK Terrain Integrated Rough Earth Model (TIREM). The TIREM install is included in the STK Pro software download, but requires a separate install process. Read the Readme.htm found in the STK install folder for installation instructions. You can obtain the necessary install by visiting http://support.agi.com/downloads or calling AGI support.

This lesson requires an internet connection and STK 12.9 or newer to complete in its entirety. If you have an earlier version of STK, you can complete a legacy version of this lesson.

The results of the tutorial may vary depending on the user settings and data enabled (online operations, terrain server, dynamic Earth data, etc.). It is acceptable to have different results.

Capabilities covered

This lesson covers the following STK capabilities:

  • STK Pro
  • Radar
  • Aviator
  • Terrain Integrated Rough Earth Model (TIREM)

Problem statement

You heard about an exercise that tested a Search/Track radar system against a small single-engine aircraft flying in rugged mountainous terrain. You want to replicate the test to determine if new radar settings will work better than the original.

Then, the second phase of the exercise tests whether an experimental aerostat with a radar jamming package could jam the tracking radar. You know in the original exercise the aerostat with a radar jamming package was tethered in a remote mountainous area 10,000 feet above ground level (AGL).

You want a scenario that simulates both phases of the test. With the simulation, you or others can further adjust parameters to study the effects against the radar.

Solution

In this lesson, you will simulate both phases of the exercise: tracking the aircraft with radar and seeing the effects of radar jamming. You will use STK's Aviator capability to create a flight path using the STK Basic General Aviation model which simulates the small aircraft. You will build a monostatic tracking radar and create a custom graph that shows the effectiveness of the Search/Track radar. Then, you will build a simulated aerostat with its attached radar jamming system. Using a custom graph, you will demonstrate how well the aerostat jammed the search track radar.

What you will learn

In this lesson, you will learn how to:

  • Insert an STK Terrain File (pdtt) for analysis and visualization using Globe Manager.
  • Build a Search/Track radar that is monostatic.
  • Specify an aircraft's radar cross section.
  • Produce a simple out and back flight route for a single engine aircraft.
  • Employ STK's TIREM capability in order to take into account how terrain affects a radar signal.
  • Create a radar which jams the Search/Track radar.
  • Design custom graphs.
  • Use constraints that customize reports and graphs.

Video guidance

Watch the following video. Then follow the steps below, which incorporate the systems and missions you work on (sample inputs provided).

Creating a new scenario

First, you need to create a new scenario.

  1. Launch STK ().
  2. Click Create a Scenario in the Welcome to STK dialog box.
  3. Enter the following in the STK: New Scenario Wizard:
    4. Option Value
    Name: Radar_Jamming
    Location: Default
    Start: 1 Apr 2024 18:00:00.000 UTCG
    Stop: + 4 hrs
  4. Click OK when finished.
  5. Click Save () when the scenario loads. A folder with the same name as your scenario is created for you in the location specified above.
  6. Verify the scenario name and location.
  7. Click Save .

Save () often!

Disabling the streaming terrain

The AGI SEDS/Geospatial Content Server distributes Earth terrain data for analysis and visualization. In this instance, you will use a local terrain file. Therefore, you will disable the streaming terrain because you do not need it for this scenario.

To use STK's Terrain Integrate Rough Earth Model (TIREM) capability, the scenario must have terrain from a local terrain file (not from a terrain server).

  1. Right click on Radar_Jamming () in the Object Browser.
  2. Select Properties () in the shortcut menu.
  3. Select the Basic - Terrain page in the Properties Browser.
  4. Clear Use terrain server for analysis.
  5. Click Apply to accept your change and to keep the Properties Browser open.

Modeling RF environment

You will track the aircraft in mountainous terrain. Therefore, you will enable TIREM to account for the mountainous terrain in the scenario.

  1. Select the RF - Environment page.
  2. Select the Atmospheric Absorption tab.
  3. Select Use.
  4. Click the Atmospheric Absorption Model Component Selector ().
  5. Select the newest TIREM model () in the Atmospheric Absorption Models list when the Select Component dialog box opens.
  6. Click OK to close the Select Component dialog box.
  7. Click Apply .

Adding a Radar Cross Sections (RCS) to the scenario

Prior to setting up and constraining a radar system, STK Radar enables you to specify an important property of a potential radar target: the Radar Cross Section (RCS).

Since you will have one object that uses an RCS, you can set the properties at the scenario level. If multiple objects required an various Radar Cross Sections, you would insert the RCS at the individual object level.

You can express RCS Values in decibels referenced to a square meter (dBsm). STK can use External Radar Files. Since you don't have an external RCS file, you will use a constant value. The small aircraft in this scenario would have a small dBsm.

  1. Select the RF - Radar Cross Section page.
  2. Enter 4 dBsm in the Constant RCS Value: field.

    3. Ideally, you would want to use an Aspect Dependent RCS file. Since you don't have one, you will use a constant value. The constant value you set is the RCS of a sphere that radiates isotropically.

  3. Click OK to accept your changes and to close the Properties Browser.

Adding a Custom Analysis Terrain Source

You will use the Custom Analysis Terrain Sources table to specify locally available terrain data files for analysis and visualization in the scenario. Although you could use the Custom Analysis Terrain Sources table while streaming terrain data from a terrain server, you don't need to do that for this lesson.

  1. Bring the 3D Graphics window to the front.
  2. Click Globe Manager () in the 3D Graphics window toolbar.
  3. Click Add Terrain/Imagery () in the Globe Manager toolbar.
  4. Select Add Terrain/Imagery... (Add Terrain/Imagery button) in the shortcut menu.
  5. Click the Path: ellipsis () in the Globe Manager: Open Terrain and Imagery Data dialog box.
  6. Browse to <STK install folder>\Data\Resources\stktraining\imagery in the Browse For Folder dialog box.
  7. Click OK to close the Browse For Folder dialog box.
  8. Select the StHelens_Training.pdtt check box.
  9. Click Add .
  10. Click Yes in the Use Terrain for Analysis dialog box.

    11. This adds visual terrain to the 3D Graphics window and enables the StHelens_Training.pdtt for analysis at the scenario level.

Inserting the first waypoint

There are multiple ways to design waypoints in STK. For this scenario, the aircraft will fly direct to waypoints that can easily be inserted into your scenario using the Place () object.

  1. Bring the Insert STK Objects tool to the front.
  2. Select Place () in the Select An Object To Be Inserted: list.
  3. Select the From City Database () method in the Select A Method: list.
  4. Click Insert... .
  5. Enter Eatonville in the Name: field in the Search Standard Object Data dialog box.
  6. Click Search.
  7. Select Eatonville (Washington) in the Results: list.
  8. Click Insert.
  9. Click Close to close the Search Standard Object Data dialog box.

Inserting the second waypoint

  1. Insert a Place () object using the Define Properties () method.
  2. Select the Basic - Position page in the Properties Browser.
  3. Make the following changes:
    4. Option Value
    Latitude: 46.1155 deg
    Longitude: -122.1957 deg
  4. Click OK to accept your changes and to close the Properties Browser.
  5. Right click on Place1 () in the Object Browser.
  6. Select Rename in the shortcut menu.
  7. Rename Place1 () to StHelens.

Visualizing waypoints in the 3D Graphics window

When using the default settings, Label Declutter declutters labels away from the central body and towards the viewer, keeping the labels from being obscured by the terrain .

  1. Bring the 3D Graphics window to the front.
  2. Click Properties () in the 3D Graphics window toolbar.
  3. Select the Details page in the Properties Browser.
  4. Select Enable in the Label Declutter frame.
  5. Click OK .
  6. Right-click StHelens_Training.pdtt in (Add Terrain/Imagery button) Globe Manager.
  7. Select Zoom To.
  8. Use your mouse to get a good view of the terrain and the waypoints.

Terrain and Waypoints

Inserting an Aircraft object

Insert an Aircraft () object.

  1. Insert an Aircraft object () using the Insert Default () method.
  2. Rename Aircraft1 () to TestFlight.

Changing the Aircraft object's propagator to Aviator

Use the Aviator propagator to simulate a small single-engine aircraft. STK's Aviator capability provides an enhanced method for modeling aircraft - more accurate and more flexible than the standard Great Arc propagator.

  1. Open TestFlight's () properties ().
  2. Select the Basic - Route page in the Properties Browser.
  3. Select Aviator for the Propagator.
  4. Click Apply .
  5. Click Optimize STK for Aviator in the Flight Path Warning dialog box.

    6. Aviator performs best in the 3D Graphics window when the surface reference of the globe is set to Mean Sea Level. You will receive a warning message when you apply changes or click OK to close the properties window of an Aviator object with the surface reference set to WGS84. It is highly recommended that you set the surface reference as indicated before working with Aviator.

  6. Click OK to close the Flight Path Warning dialog box.

Mission window

The Mission Window is used to define the aircraft's route when Aviator has been selected as the propagator.

Mission Window

Selecting an aircraft model

The buttons on the Initial Aircraft Setup toolbar are used to define the aircraft model that will be used in the mission.

The User Aircraft Models represent of different types of aircraft. They don't contain actual specifications for any one type of aircraft but their properties are close to the type of aircraft selected. If you desire to build an aircraft to your specifications, you would duplicate the desired type and then edit that type to match your aircraft.

Select the aircraft to be used for the Mission.

  1. Click Select Aircraft () on the Initial Aircraft Setup toolbar.
  2. Select Basic General Aviation on the Select Aircraft dialog box.
  3. Click OK to close the Select Aircraft dialog box.
  4. Click Apply .

Setting Eatonville as the first waypoint

Although Aviator allows you to design the complete flight route (takeoff through landing), this test only models the time when the aircraft flew from Eatonville to StHelens and back. You will select Eatonville as the aircraft's first waypoint. STK Static Object Waypoints are used to define a waypoint at the position of another, stationary, object within the scenario over time.

Inserting the first Procedure

  1. Right-click on Phase 1 in the Mission List.
  2. Click Insert First Procedure for Phase... () in the shortcut menu.

Setting Eatonville as a Static Object waypoint

  1. Select STK Static Object () in the Select Site Type: list when the Site Properties dialog box opens.
  2. Type Eatonville in the Name: field.
  3. Select Eatonville () in the Link To: list.
  4. Click Next > .

Selecting the Procedure type

A Basic Point to point procedure travels a straight line through 3D space from the end of the previous procedure to the site of the current procedure.

  1. Select Basic Point to Point () in the Select Procedure Type: list in the Procedure Properties dialog box.
  2. Click Finish .
  3. Click Apply .

Setting StHelens as the second waypoint

You will select StHelens as the aircraft's second waypoint.

Inserting the next Procedure

  1. Select Eatonville in the Mission List.
  2. Click Insert Procedure After... () in the Procedures and Sites toolbar.

Setting StHelens as a Static Object waypoint

  1. Select STK Static Object () in the Select Site Type: list in the Site Properties dialog box.
  2. Type StHelens in the Name: field.
  3. Select StHelens in the Link To: list.
  4. Click Next > .

Selecting the Procedure type

  1. Select Basic Point to Point () in the Select Procedure Type: list in the Procedure Properties dialog box.
  2. Clear Use Aircraft Default Cruise Altitude in the Altitude frame.
  3. Enter 9000 ft in the Altitude field in the Altitude frame.
  4. Select Arrive on Course for Nav Mode in the Navigation Options frame.
  5. Enter 90 deg for the course.

    6. When the aircraft gets to the StHelens waypoint, setting the Nav Mode to Arrive on Course and setting the course to 90 degrees true places the aircraft on a heading The direction that the aircraft is pointing. of 90 degrees at StHelens.

  6. Click Finish .
  7. Click Apply .

Returning to Eatonville

Now model the return to Eatonville.

Inserting the next Procedure

  1. Select StHelens in the Mission List.
  2. Click Insert Procedure After... () in the Procedures and Sites toolbar.

Setting Eatonville as a Static Object waypoint

  1. Select STK Static Object () in the Select Site Type: list in the Site Properties dialog box.
  2. Type Return to Eatonville in the Name: field.
  3. Select Eatonville in the Link To: list.
  4. Click Next > .

Selecting the Procedure type

  1. Select Basic Point to Point () in the Select Procedure Type: list in the Procedure Properties dialog box.
  2. Click Finish .
  3. Click Apply .

Disabling the line-of sight-constraint

Since you are using TIREM, you should turn off the line-of-sight constraint.

  1. Select the Constraints - Active page.
  2. Clear Enable for Line Of Sight in the Active Constraints list.
  3. Click OK .

To make the most efficient use of the TIREM analysis, you should disable Line-of-sight, Terrain Mask, or Az-El Mask constraints to take advantage of the over-the-horizon analysis capabilities of TIREM.

Viewing the flight route

With the aircraft flight route modeled, view the flight path you made.

  1. Bring the 3D Graphics window to the front.
  2. Use your mouse to get a good view of TestFlight () and both waypoints.

TestFlight and Waypoints

Modeling the Radar site

The tracking radar is located at a small regional airport.

  1. Insert a Place () object using the Define Properties () method.
  2. Select the Basic - Position page in the Properties Browser.
  3. Make the following changes:
    4. Option Value
    Latitude: 46.6774 deg
    Longitude: -122.9858 deg
  4. Click OK .
  5. Rename Place2 () to RadarSite.
  6. Zoom to RadarSite.

    7. You will model the radar using selected specifications from an airport tracking radar. However, instead of creating a spinning antenna, you will lock the antenna onto the aircraft. This is a good way to determine if you can track your target when using STK's radar capability.

Modeling a Sensor object

The Radar () object's antenna can be bore-sited. However, in STK, if you have an antenna that can track another object, use a Sensor () object as the servo motor.

  1. Insert a Sensor () object using the Insert Default () method
  2. Select RadarSite () in the Select Object dialog box.
  3. Click OK.
  4. Rename Sensor1 () to Servo.

Changing Servo's properties

You will use the Sensor () object's projection for situational awareness (where the antenna is pointing).

  1. Open Servo's () properties ().
  2. Select the Basic - Definition page in the Properties Browser.
  3. Enter 1 deg in the Cone Half Angle: field in the Simple Conic frame.
  4. Click Apply.

Repositioning Servo

Servo () (the child object ) is attached to the center point of RadarSite () (the parent object). In this analysis, the antenna needs to be 50 feet in altitude.

Facility, place and target objects have body-fixed coordinate axes, which align the x-axis along local horizontal North direction, the y-axis along local horizontal East direction, and the z-axis along local Nadir direction.

You want to leave RadarSite () on the ground, but you want to move Servo () up in altitude. In STK, you move the child along the parent's axis. In this instance, if you want to move the Servo () up in altitude, you will use RadarSite's () Z body. Since the positive Z points to Nadir (down), you will use a negative value to move Servo () up along RadarSite's () Z body.

  1. Browse to the Basic - Location page.
  2. Select Fixed for the Location Type.
  3. Enter -50 ft in the Z: field.
  4. Click Apply .

Viewing Servo in the 3D Graphics window

  1. Bring the 3D Graphics window to the front.
  2. Notice the Servo () is elevated in altitude (50 feet).

Sensor Object and Place Object Locations

Targeting the Aircraft

As stated earlier, the radar will lock on to the Aircraft. The Sensor () object is acting as a servomotor. Target the sensor which in turn will target the antenna later in the lesson.

  1. Return to Servo's () properties ().
  2. Select the Basic - Pointing page.
  3. Select Targeted for Pointing Type.
  4. Move () TestFlight () from the Available Targets list to the Assigned Targets list.
  5. Click Apply.

Setting Servo's constraints to use TIREM

You should turn off the line of sight constraint on objects using TIREM.

  1. Select the Constraints - Active page.
  2. Clear Enable - Line Of Sight.
  3. Click OK .

Viewing Servo track the TestFlight aircraft

  1. Bring the 3D Graphics window to the front.
  2. Click Increase Time Step () to set your X Real Time Multiplier to 8:00 which you can see in the 3D Graphics window.
  3. Click Start () in the Animation toolbar to animate your scenario.

    4. As you watch the Sensor object track the aircraft , you will see that, at times, you have unobstructed line of sight. At other times, the aircraft dips behind terrain. Both the terrain and distance from the radar site will affect how well your radar can track the aircraft.

    Sensor Tracking Aircraft

  4. Click Reset () to reset your scenario to the start time when finished.

Modeling the tracking radar

For this analysis, you will use a single beam. The Radar () object will be a child of the Servo (). Since Servo () is bore sighted towards TestFlight (), the Radar () object's embedded antenna, which is pointing along the parent's Z body, will also point at TestFlight (). (Orientation Methods)

  1. Insert a Radar () object using the Insert Default () method.
  2. Select Servo () in the Select Object dialog box.
  3. Click OK.
  4. Rename Radar1 () to Tracking_Radar.

Modeling a monostatic radar

You will model a monostatic radar using a search track mode. You could use this type of antenna for transmitting and receiving, along with detecting and tracking point targets.

To understand constants and equations used in STK, look at Search/Track Radar Constants and Equations in STK Help.

Inserting a monostatic radar

  1. Open Tracking_Radar's () Properties ().
  2. Select the Basic - Definition page.
  3. Notice the Radar System defaults to Monostatic.
  4. Select the Mode tab.
  5. Notice the Radar Monostatic Mode defaults to Search Track.

Defining the waveform

The PRF is the number of pulses of a repeating signal in a specific time unit. After producing a brief transmission pulse, the transmitter turns off in order for the receiver to hear the reflections of that signal off of targets.

  1. Select the Waveform sub-tab.
  2. Notice the Waveform is set to Fixed PRF.

Defining the pulse width

The waveform in your system will use a fixed pulse repetition frequency (PRF) of approximately 2000 Hz. Pulse width is the width of the transmitted pulse (the uncompressed RF bandwidth can also be taken as the inverse of the pulse width). You will set the pulse width to one microsecond.

  1. Select the Pulse Definition sub-sub-tab.
  2. Enter 0.002 in the PRF field.
  3. Enter 1 usec in the Pulse Width: field.

Setting Probability of Detection

STK Radar implements a Swerling detection model. The probability of detection is a function of the per pulse signal to noise ratio (SNR), the number of pulses integrated, the probability of false alarm and the radar cross section (RCS) fluctuation type.

  1. Select the Probability of Detection sub-sub-tab.
  2. Enter 1e-06 in the Probability of False Alarm: field.

Setting Pulse Integration

Radar systems often use multiple pulse integration which is the process of summing all the radar pulses to improve detection. This helps increase the signal-to-noise ratio.

  1. Select the Pulse Integration sub-sub-tab.
  2. Select Fixed Pulse Number in the pull-down menu.
  3. Enter 5 in the Pulse Number: field.
  4. Click Apply .

Setting antenna specifications

Select the radar's antenna pattern and change its design to particular specifications.

  1. Select the Antenna tab.
  2. Click the Antenna Model Component Selector ().
  3. Select Pencil Beam () in the Antenna Models list in the Select Component dialog box. (Pencil Beam Antenna).
  4. Click OK to close the Select Component dialog box.
  5. Enter 3 GHz in the Design Frequency: field.
  6. Click Apply.

Building the transmitter

Update the frequency and power for the radar's transmitter.

  1. Select the Transmitter tab.
  2. Select the Specs sub-tab.
  3. Select the Frequency option.
  4. Enter 3 GHz in the Frequency field.
  5. Enter 25 kW in the Power: field.
  6. Click Apply.

Building the receiver

The radar's receiver has a pre-receive gain of five (5) dB.

  1. Select the Receiver tab.
  2. Select the Additional Gains and Losses sub-tab.
  3. Click Add in the Pre-Receive Gains/Losses frame.
  4. Enter 5 dB in the Gain cell.
  5. Click Apply .

Setting the constraint to use TIREM

The last step is to ensure that TIREM is used in the analysis.

  1. Browse to the Constraints -  Active page.
  2. Clear Enable - Line Of Sight.
  3. Click OK .

Analyzing the Radar

You are ready to determine the radar's tracking ability. The first step is to determine how well your radar can track the aircraft.

  1. Right-click on Tracking_Radar () in the Object Browser.
  2. Select Access... ().
  3. Select TestFlight () in the Associated Objects list in the Access Tool.
  4. Click .

Creating a custom graph

For your analysis, you are interested in two report contents, S/T Integrated PDet (Search/Track Integrated Probability of detection) and Range. The radar uses five pulses for integration. The process of summing all the radar pulses to improve detection is known as “Pulse integration." By creating a custom graph that contains these contents, you can quickly determine the effectiveness of your radar.

Creating a new graph

  1. Click Report & Graph Manager... in the Access Tool.
  2. Select My Styles () in the Styles frame when the Report & Graph Manager opens.
  3. Click Create new graph style () in the Styles toolbar.
  4. Type PDet and Range as the graph's name.
  5. Click Enter on your keyboard to the set the name and to open the Properties Browser.

Selecting the data providers

The content of a report or graph is generated from the selected data providers for the report or graph style.

  1. Select the Content page in the Properties Browser.
  2. Expand () the Radar SearchTrack () data provider.
  3. Move () the S/T Integrated PDet () element from the Data Provider list to the Y Axis list.
  4. Expand () the AER Data () data provider.
  5. Expand () the Default () group.
  6. Move () the Range () element to the Y2 Axis list.
  7. Click OK .

Generating the new graph

  1. Select PDet and Range () in My Styles ().
  2. Click Generate... .

    3. S/T Integrated PDet Range Graph

    You are looking for a PDet of 0.8 or greater. It's a given that as distance increases, your PDet will decrease. There are instances where your tracking drops well below a PDet of 0.8. Using the Toggle animation time line button, right-clicking on the graph, and selecting Set Animation Time, you can jump back to the 3D Graphics window to visualize what is occurring.

    Overall, the radar system is able to track the aircraft when it's within range and unobstructed by terrain.

  3. Close the graph, the Report & Graph Manager, and the Access Tool.

Inserting an aerostat into the scenario

You will simulate an aerostat flying near Mount St. Helens. The aerostat is tethered at 10,000 ft above ground level (AGL). An easy way to do this in STK, if you're not taking drift into your analysis, is by using a Place () object.

  1. Insert a Place () object using the Define Properties () method.
  2. Select the Basic - Position page in the Properties Browser.
  3. Make the following changes:
    4. Option Value
    Latitude 46.1173 deg
    Longitude -122.315 deg
    Height Above Ground 10000 ft
  4. Click OK .
  5. Rename the Place3 () to Aerostat.

Adding the Aerostat radar jammer

You can model the radar jammer by simply reusing the previously built tracking radar and making a couple of changes.

  1. Right click on Servo () in the Object Browser.
  2. Select Copy ().
  3. Right click on Aerostat () in the Object Browser.
  4. Select Paste ().
  5. Rename Servo1 () to Jam_Servo.
  6. Rename Tracking_Radar1() to Jammer.

Repositioning Jam_Servo

Jam_Servo () is attached to Aerostat () but it's floating 50 feet above it. Attach Jam_Servo () to Aerostat's () center point so that it's at the same altitude.

  1. Open Jam_Servo's () properties ().
  2. Select the Basic - Location page.
  3. Change Location Type to Center.
  4. Click Apply.

Targeting the airfield search and track radar

When Jammer () radiates, you are placing "noise" on Tracking_Radar's () receiver.

  1. Select the Basic - Pointing page.
  2. Remove () TestFlight () from the Assigned Targets list.
  3. Move () RadarSite () from the Available Targets list to the Assigned Targets list.
  4. Click OK .

Viewing your progress in the 3D Graphics window

  1. Bring the 3D Graphics window to the front.
  2. Zoom To Aerostat ().

Aerostat

Defining the jammer's antenna

Aerostat is tethered at 10,000 ft AGL. Jam_Servo () is attached to Aerostat's () center point and is targeting RadarSite (). Make the required specification changes to Jammer ().

  1. Open Jammer's () properties ().
  2. Select the Basic - Definition page in the Properties Browser.
  3. Select the Antenna tab.
  4. Select the Model Specs sub-tab.
  5. Click the Antenna Model Component Selector ().
  6. Select Square Horn () in the Antenna Models list in the Select Component dialog box.
  7. Click OK to close the Select Component dialog box.
  8. Enter 3 GHz in the Design Frequency: field.
  9. Enter 1 ft in the Diameter: field.

Defining the jammer's transmitter

  1. Select the Transmitter tab.
  2. Select the Specs sub-tab.
  3. Enter 1 W in the Power: field.
  4. Click OK .

Jamming the radar

The next step is to tell the tracking radar that it's being jammed.

  1. Open Tracking_Radar's () properties ().
  2. Select the Basic - Definition page in the Properties Browser.
  3. Select the Jamming tab.
  4. Select Use.
  5. Move () Aerostat/Jam_Servo/Jammer () to the Assigned Jammers list.
  6. Click OK .

Determining the jammer's effectiveness

You are now ready to analyze the radar jammer's effectiveness against the tracking radar. Create a custom graph that shows only those contents you are interested in for your analysis. You are interested in S/T Integrated PDet and S/T Integrated PDet w/ Jamming (Search/Track Integrated Probability of detection with jamming).

Creating a new graph

  1. Right-click on Tracking_Radar () in the Object Browser.
  2. Select Access... ().
  3. Select TestFlight () in the Associated Objects list in the Access Tool.
  4. Click Report & Graph Manager... .
  5. Select My Styles () in the Styles frame in the Report & Graph Manager.
  6. Click Create new graph style () in the Styles toolbar.
  7. Type PDet Jamming to name your graph.
  8. Click Enter on your keyboard to the set the name and to open the Properties Browser.

Selecting the data providers

Select the data providers and elements for your graph.

  1. Select the Content page in the Properties Browser.
  2. Expand () the Radar SearchTrack () data provider.
  3. Move () the S/T Integrated PDet to the Y Axis list.
  4. Move () the S/T Integrated PDet w/ Jamming to the Y Axis list.
  5. Click OK .

Generating the new graph

  1. Select PDet Jamming () in My Styles ().
  2. Click Generate... .

    3. By placing the S/T Integrated PDetand S/T Integrated PDet with jamming on the same axis, it's easier to read the graph. As you can see by looking at the graph, the jammer attached to the aerostat is effectively jamming the tracking radar.

    S/T Integrated PDet With Jamming

    Your graph might look slightly different from the above image. You can see from the graph that the radar jammer effects the return signal back to the radar's receiver. You can also see that it doesn't take a lot of power for an interference source to affect the radar.

  3. Close () the graph.

Generating a radar jamming report

Run a report that will show the jammer's affect against the tracking radar. This report will provide a comparison of the probability of detection with or without jamming.

  1. Retun to the Report & Graph manager.
  2. Select the Radar SearchTrack with Jamming () report in Installed Styles ().
  3. Click Generate.
  4. Four columns of data might be of interest in this report. Start by looking at S/T PDet1 and S/T PDet1 w/Jamming (single pulse) and compare it to S/T Integrated PDet and S/T Integrated PDet w/Jamming. This gives a good example of how integration provides better tracking than single pulse.

Adding a Search/Track Constraint

In the report, you are looking for instances greater than or equal to 0.8 in the S/T Integrated PDet column. Any instance greater than or equal to 0.8 is when the Tracking_Radar can see TestFlight. Add a Min Integrated PDet constraint to Tracking_Radar.

  1. Open Tracking_Radar's () properties.
  2. Select the Constraints - Active page.
  3. Click Add new constraints () in the Active Constraints toolbar.
  4. Select Integrated PDet in the Constraint Name list in the Select Constraints to Add dialog box.
  5. Click Add.
  6. Click Close to close the Select Constraints to Add dialog box.
  7. Enter 0.8 in the Min: field in the Integrated PDet frame in the Constraint Properties section
  8. Click Apply.

Refreshing your report

  1. Bring the Radar SearchTrack with Jamming () report to the front.
  2. Click Refresh (F5) () the report's toolbar.
  3. Notice that access duration has been reduced, and all S/T Integrated PDet values are equal to or greater than 0.8.

    4. The report is only showing those times when Tracking_Radar () is able to track TestFlight () based on S/T Integrated PDet without jamming. This makes it easier to compare those times against the effects of the jamming radar.

Determining when the radar jammer is effective

You can further modify the report by selecting the Integradted PDet w/Jamming constraint and enabling the Min: field with a value of 0.8. This would show when Jammer is effective.

  1. Return to Tracking_Radar's () properties.
  2. Click Add new constraints () in the Active Constraints toolbar.
  3. Select Integradted PDet Jamming in the Constraint Name list in the Select Constraints to Add dialog box.
  4. Click Add.
  5. Click Close to close the Select Constraints to Add dialog box.
  6. Clear the Min: check box in the Integrated PDet Jamming frame.
  7. Enter 0.8 in the Min: field.
  8. Click OK.

Refreshing your report

  1. Bring the Radar SearchTrack with Jamming report to the front.
  2. Click Refresh (F5) () the report's toolbar.

    3. The report is showing those times when the jammer is affecting your link.

Save your work

  1. Close any open reports, properties and tools.
  2. Save () your work.

Summary

This scenario determined that a ground based tracking radar successfully tracked a small aircraft in mountainous terrain. For the most part, tracking was successful except in those instances when the plane was behind the mountains. The second half of the scenario determined that an aerostat radar jamming system effectively jammed the ground based radar. Based on the radar jammer's specifications, you know that the jammer worked well against the tracking radar.

On your own

Try adjusting the tracking radar's pulse count, frequency or PRF. Different combinations will effect the tracking radar's efficiency. Incrementally increase the jammer transmitter's power by 1 watt at a time to find the power needed to completely jam the tracking radar.