The plan check
Every row of the plan is checked after every change — spacing, 3rd- and 5th-order intermod, blocked spectrum. What the ⚠ reasons mean, how to clear them and why the export asks first.
On this page
A plan can go wrong after the packer is done with it: you add a row, import a WWB file, load last month's plan in another region, or import a scan that shows a carrier right where a channel sits. So FreqSense checks the whole plan, on every row, after every change — adding, editing, importing and loading.
The line under the table
- Plan check: clean (green) — every row passed: spacing, 3rd- and 5th-order intermod (two and three transmitters) and blocked spectrum.
- Plan check: n intermod hits · n in blocked spectrum · n too close — some rows have a problem. Each of them carries ⚠ in the table.
What a ⚠ means
Hover or focus the ⚠ on a row to read its reasons:
| Reason | What it means | How to clear it |
|---|---|---|
| Only X kHz from Y MHz | Closer than 250 kHz to another row — a typical receiver cannot separate the two. | Delete one of the two rows, or press Recompute to re-pack the band. |
| Intermod hit: … (order 3) / (order 5) | A 3rd-order (2A−B, A+B−C) or 5th-order (3A−2B) product of your own transmitters lands on this row. The label names the frequencies that mix. | Re-pack the band with Recompute, or delete a row that takes part in the product. |
| In blocked spectrum X–Y MHz | The row sits where the region's rules do not allow it, in a mobile or protected band, or in a range your scan marked as occupied. | Check the Region first. Otherwise re-pack, or remove the scan if it was taken somewhere else. |
The same problems are marked on the spectrum, and the printed sheet has a Check column with the reason per row.
With several bands in one plan, a mic and an IEM row can hit each other. Recompute re-packs only the selected band, clean against all other rows — so re-pack the band whose rows are easiest to move.
Export asks first
↓ WWB and ↓ WSM hand out a plan with problems only after you confirm: This plan has n problems (⚠ in the table). Export it anyway? — Export anyway or Cancel. A clean plan exports straight away.
Adding to a plan that already has hits
+ Add row and Coordinate look for frequencies clean against every row. If the plan already has intermod hits, the toast says The plan already has intermod hits — fix the ⚠ rows or press Recompute first: fix the plan before you grow it.
The check covers your plan against itself, the region's rules and your scan. It does not know which local TV transmitters are on air — a clean check without a scan is clean against what FreqSense knows, not against the room. See Import a scan.
Thanks for the feedback.