Frequency Plan Intermodulation Checker

Also known as Frequency Plan Validator

Check an existing or proposed radio frequency plan for intermodulation products on or near its carriers, graded to ITU-R SM.1134-1, ACMA RALI LM 08 Table D2 or a custom separation.

Pro ● Live 2 standards

Included in the 14-day Pro trial on every new account. No credit card.

System mode and site details.

Walkthrough

See it working

Step 01

Open a project

Resume a saved plan, import a project file or start a new project. A plan handed over from the Frequency Coordination Tool or the Frequency Plan Optimiser opens as a new project.

System mode and site details.
Single carriers, repeater pairs and bulk entry.
Step 04

Choose the hit criterion and model settings

Choose the rule that sets the direct hit boundary: ITU-R SM.1134-1, RALI LM 08 Table D2 for surface plans, or a custom separation. Decide whether a product exactly on the boundary passes, then adjust the zone offsets, roll-off model, noise floor, isolation and scoring options if needed.

Score, grade and hit zone breakdown.
Hit table with formulae, contributors, zones and margins.
Spectrum view with direct hits highlighted.

Overview

Check a radio frequency plan for intermodulation hits

Many radio sites collect intermodulation problems over time as channels are added, splits change and new services move in nearby. Range shortens and intermittent interference appears, and the cause is not always obvious. Before replacing hardware or redesigning the plan, the first question is whether the existing frequencies are producing intermodulation products on the site's own channels, and if so, where.

Read the full overview

The Frequency Plan Validator answers that question without changing the plan. It enumerates the intermodulation products of every carrier combination, second, third and fifth order in surface mode and second and third order in underground mode, and checks each product against every carrier. Hits are graded in zones that scale with each carrier's bandwidth, and the direct hit boundary follows the rule you choose: half the channel bandwidth under ITU-R SM.1134-1, the Annex D Table D2 offsets of ACMA RALI LM 08 for surface plans, or a custom separation.

On top of the frequency arithmetic, the validator estimates each product's level from the transmit power, an intermodulation roll-off model and the transmit to receive isolation, and compares it with the victim receiver noise floor. Results include a score and grade, a full hit table, a hit summary by downlink and uplink leg, source and victim impact tables and a spectrum view, with PDF and CSV reports that state the rule used. Calculations run in your browser, and each plan is saved as a project in your account.

Capabilities 8

Bandwidth aware hit zones

Each product is graded by its separation from the carrier it lands near, scaled to that carrier's bandwidth. A direct hit falls inside the chosen boundary, and three further zones mark critical, marginal and watch separations beyond it, with offsets you can adjust.

A choice of cited hit criterion

The direct hit boundary can follow ITU-R SM.1134-1 (half the channel bandwidth), ACMA RALI LM 08 Annex D Table D2 for surface plans, or a custom separation. Under LM 08, products the table does not cover are reported as not assessed, and the summary, CSV and PDF all state which rule was used and how a product exactly on the boundary was read.

Surface and underground modes

Surface mode checks second, third and fifth order products, excludes receive-only carriers as sources and applies transmit to receive isolation. Underground mode checks second and third order products, treats every carrier alike as on a leaky feeder, and lets you choose whether downlink and uplink carriers combine.

Transmit landings kept separate

A product landing on a transmit-only carrier is listed in its own section rather than scored, because nothing at the site listens on that frequency. It is still reported, because mobiles in the field may be listening there.

Predicted level and margin above noise

Each hit carries an estimated level at the victim and its margin above the receiver noise floor. The score can count hits at face value or weight them by predicted level, so a product well below the noise floor does not dominate the result.

Hit table, impact tables and spectrum view

The hit table lists every product with its order, formula, contributors, victim, separation and zone. Impact tables show each carrier as a source and a victim, the pairs that cause the most hits and the hits on each repeater pair, and a spectrum view overlays the products on the carriers.

PDF and CSV reports

A PDF report collects the site details, parameters, summary, hit table, impact tables and spectrum plots. The CSV export carries the full hit table with a preamble naming the criterion, so another engineer can review it line by line.

Projects and hand-off

Each plan is a project that saves to your account and can be exported or imported as a file. A Frequency Coordination or Frequency Plan Optimiser result opens here as a new project, already set to the separation it was planned to.

Inputs and outputs

What goes in, what comes out

Inputs 10

  • Carriers entered singly or as downlink and uplink repeater pairs
  • Label, frequency, bandwidth and transmit power for each carrier
  • Bulk entry from a CSV template or pasted rows
  • System type: surface or underground
  • Hit criterion: ITU-R SM.1134-1, RALI LM 08 Table D2 or a custom separation
  • Whether a product exactly on the boundary passes
  • Zone offsets, intermodulation roll-off, noise floor, isolation and band gap
  • Harmonic suppression and power weighted scoring options
  • Site details for the report
  • A saved project file, or a plan from the Coordination Tool or Optimiser

Outputs 9

  • Plan score and grade
  • Hit zone breakdown with the direct hit boundary stated
  • Hit table with formulae, contributors, separation, zone, predicted level and margin
  • Hit summary by downlink, uplink and unpaired carrier
  • Transmit landings listed separately
  • Source and victim impact, pair interaction and repeater pair tables
  • Most impacted channels and most problematic pairs
  • Spectrum view with direct hits highlighted
  • PDF report and CSV export naming the criterion

Standards & methodology

  • ITU-R SM.1134-1 section 3.1: a direct hit within half the channel bandwidth (default criterion)
  • ACMA RALI LM 08 section 6.5.3 and Annex D Table D2: hit range by interferer width, receiver width and order, for surface plans

Use cases

When to use this tool

  1. 01Auditing an operational radio system before a maintenance shutdown
  2. 02Checking a plan proposed by a vendor or consultant before acceptance
  3. 03Finding which carriers are behind interference complaints
  4. 04Checking a new channel against an existing plan before programming radios
  5. 05Grading a surface plan to RALI LM 08 Table D2 at face value
  6. 06Checking a Frequency Coordination or Optimiser result at the separation it was planned to
  7. 07Producing an intermodulation appendix for an engineering report
  8. 08Comparing surface and underground analysis for a mine with both kinds of system

FAQ

Frequently asked questions

Not here? Ask us

How is this different from the Frequency Plan Optimiser?

The validator reports where intermodulation hits land in a plan without changing it. The optimiser proposes small channel shifts to reduce those hits. An optimiser result opens here with the same product set and separation, so the two tools agree on what counts as a hit.

Which hit criterion should I use?

ITU-R SM.1134-1, with the direct hit boundary at half the channel bandwidth, is the default and matches the Intermodulation Calculator. ACMA RALI LM 08 Table D2 reads the hit range by interferer width, receiver width and order and is usually wider, so a plan that is clean at half bandwidth can still show LM 08 hits. A custom separation grades every carrier to one value, which is how a coordination result arrives.

What does bandwidth aware mean?

The hit zones scale with each carrier's own bandwidth rather than one value for the whole plan. A wideband channel therefore has a wider direct hit zone than a narrowband one, so a plan that mixes channel widths is graded fairly.

Which intermodulation orders are checked?

Surface mode checks second, third and fifth order products, both two signal and three signal, with receive-only carriers excluded as sources. Underground mode checks second and third order products and leaves out fifth order. Single carrier harmonics are suppressed by default and can be included.

Does a clean result under RALI LM 08 mean a plan will be licensed?

No. The validator applies the Table D2 hit ranges at face value to the carriers you enter, and reports the products the table does not cover as not assessed. It does not carry out the frequency assignment process, and the ACMA decides whether a frequency is assigned.

How is the predicted level worked out?

The level at the transmitter is the lowest contributing transmit power less a roll-off for the product's order. In surface mode the transmit to receive isolation is then subtracted, and the result is compared with the victim receiver noise floor to give the margin. Each of these values can be set for the project.

Where is my data kept?

The analysis runs in your browser, and no carrier list is sent to a server to be validated. Each plan is saved as a project in your browser and in your noIM₃ account so it follows you across devices, and it can be exported as a project file.

What do the PDF and CSV contain?

The PDF report includes the site details, analysis parameters, summary, hit table, impact tables and spectrum plots. The CSV holds the full hit table and opens with a preamble that names the hit criterion and boundary reading, so each hit can be traced to the rule it was graded against.

Free for 14 days

Included in the 14-day Pro trial on every new account. No credit card.