New plugin

Airchain

FM radio airchain emulation — AGC, four-band squash, emphasis, clipper and transmission artifacts behind one big SQUASH knob.

VST3 / AUmacOS14 presets
Discover Airchain
support@squaresmile.de Köln, Germany
All guides

Help Center · FreqSense

Troubleshooting

Rows with ⚠, empty windows, packer shortfalls, scan files that will not parse, a plan replaced by mistake and plans that did not sync.

Open FreqSense

Symptom Likely cause & fix
A row shows ⚠ The plan check found a problem on that row. Hover the ⚠ for the reason — too close, an intermod hit, or blocked spectrum. See The plan check.
Export asks This plan has n problems … Export it anyway? The plan check found ⚠ rows. Cancel, fix them, export again — or export anyway if you know why.
Toast The plan already has intermod hits + Add row or Coordinate cannot find a clean frequency next to a broken plan. Fix the ⚠ rows or press Recompute first.
Windows panel says Pick your hardware to see free windows No band is selected. Pick a Manufacturer / Band, or import a scan. You can still print the regional whitespace.
No windows ≥ X MHz Min width is higher than any gap in this band. Lower it, or zoom the spectrum to check whether the band sits in mobile spectrum.
Coordinate button is disabled The packer needs a manufacturer band. Select one above.
Y requested, X placed — try a larger spacing The band ran out of intermod-free room. Reduce N, change the Channel spacing or choose a band that reaches more usable spectrum. With several bands in the plan, the other bands' rows take room too.
Toast Band full when adding a row Same cause — no clean room at the current spacing.
No clean backup left in this band Every clean frequency in the band is taken. Lower the Backups count, or free room in the plan.
Toast Lost: … after Coordinate The re-pack produced fewer slots than you have named rows; the names listed lost their row. Raise N and press Coordinate again.
Coordinating the IEM band moved my mics It does not: re-coordinating a band re-packs only that band. Check which band is selected — the gear name under each talent says which band a row belongs to.
I cleared, loaded or imported over a plan by mistake Press Undo in the toast — it puts the previous plan back exactly.
A window looks free, but there is a signal at the venue FreqSense does not know which local TV transmitters are on air. Import a scan — see Import a scan.
A German band outside 400–960 MHz (174–230, 1350–1400, 1785–1805 MHz) is not on the spectrum The spectrum covers 400–960 MHz. Those bands are listed in the regulatory table only; FreqSense does not coordinate them.
Scan import: no valid data points found The file is not one of the supported formats. Save it as a plain two-column CSV (frequency in MHz, level in dBm) and retry. RF Explorer's binary file is not read — export CSV.
Scan import: many lines rejected Wrong units or an odd header. The warning names the first bad line; check that frequencies are in MHz, kHz or Hz consistently. ; separators and decimal commas are fine.
Trace limit reached (3) Remove a trace, or accept the prompt to replace the oldest.
Imported WWB/WSM plan: Format unrecognized Set Force format to WWB or WSM.
Imported plan: fall outside the selected region's allocations The plan was made for another country. Change Region first.
File too large (max 1 MB) Remove unused columns or split the CSV.
Plan references scan "…" after loading a plan Plans store which scan they used, not the data. Import the same scan file again.
Toast Saved plans are not synced right now No connection, or the sync failed. The plans stay on this device and sync when the connection is back.
Plan saved on one device is missing on another Both devices must be signed in to the same account and online. Reload — the toast Account data arrived means a newer copy has just come in. See Account sync.
Save failed — storage unavailable The browser is blocking storage (private mode or full). Use a normal window or free up space.
Print view is missing the coordination table Nothing was placed. Run Coordinate or add rows, then print again.

Spectrum looks wrong for my country

Check Region / Regulatory Framework first — it is the single input everything else depends on. Spain has no region of its own: use EU and read Spain's row in the regulatory table. If the region is right and a band still looks wrong, open the Source linked for that band, compare it with the German write-up at /rf-cheatsheet/funkfrequenzen-deutschland (for DE) or your regulator's current order, and treat the regulator as the authority.

Was this page helpful?