A Spectral Scan measures the radio energy across the whole US915 band, 902–928 MHz. Unlike the
LoRaWAN scan, it also sees transmitters that aren't LoRaWAN, such as RFID readers, wireless microphones or meter
networks.
Measures the radio energy across the whole US915 band, 902–928 MHz, with the gateway's second radio
(SX1261). Unlike the LoRaWAN scan, it also sees transmitters that aren't LoRaWAN, such as RFID readers, wireless
microphones or meter networks. Run it before a LoRaWAN scan to find out whether the band is usable here, and which
sub-bands are quietest.
LoRa is switched off while it runs (one sweep of the band takes about 15 seconds) and switched
back on afterwards; the gateway's saved settings are not changed. When it finishes, no scan runs until you start
one, so you can look at the results first. To scan LoRaWAN traffic next, choose LoRaWAN Traffic Scan in Configure
scanning and press Start Scan. It needs a sign-in.
Noise floor · dB above the quietest channels
Other signals · share of samples at least 8 dB above the channel's own floor
Sub-band
Frequencies
Noise floor
Signals (avg / busiest)
Busiest channel
Verdict
Levels are relative: the gateway's spectral readings are about 4 dB per step and not
calibrated to dBm, so the noise floor is shown against this gateway's quietest channels. A floor 8 dB or more
above the quietest means devices at the edge of range may not be heard there. Hover over a bar for its frequency.
LoRaWAN Traffic Scanner
Welcome to the MultiTech LoRaWAN Traffic Scanner. This application will allow you to see how
busy various LoRaWAN bands are and which ones are ideal for use in your environment. Click Next to proceed or
Cancel.
1. Sign in to the gateway
Enter the gateway's mPower admin login. The scanner uses it once to create its own mPower user
(lorawan-scanner) for the changes it makes, so it won't lock you out of the mPower web page. The admin
password isn't kept.
Signing in and setting up the scanner's mPower user. Please wait 10-60 seconds for the next page
to appear.
2. Back up the gateway (recommended)
Before the app changes any LoRaWAN setting, save a copy of the gateway's configuration to your computer. If
anything goes wrong, you can restore it in mPower under Administration › Save/Restore.
Tick what to save, then click Save Selected Files. The files go to your browser's Downloads folder.
You can go on to the next step whether or not you made a backup.
3. The settings the scanner needs
Checking the gateway's LoRaWAN settings…
Setting
Now
Needed
This gateway is serving a LoRaWAN network
While it is set up for scanning, those devices can't reach their network. Put the settings back after the
scan (Settings › Gateway Readiness Check › User defined settings).
The app will make these changes in mPower:
Everything else, including the sub-band, stays as it is. The app saves the change and restarts
LoRa (about 10 seconds, no reboot). It records the current settings first, so you can put them back after the
scan (Settings › Gateway Readiness Check › User defined settings).
Firewall: the app has automatically created a firewall rule so your browser can reach this
page (TCP 8080 on the gateway's LAN). It isn't listed with mPower's firewall rules, and it is removed
automatically when the app is stopped or deleted from Apps › Custom Apps.
4. Choose a scan
4. Choose the type of LoRaWAN scan
The scanner listens on whatever sub-band the gateway is already set to and never changes the radio.
Choose it when the gateway must stay on its sub-band, for example one that goes back into service right
after, or when you only need to know about the sub-band your own network uses. It is the least disruptive
choice, but it tells you about one sub-band only.
The scanner sets the radio to the sub-band you choose and stays there, hearing all of its traffic.
Choose it to watch one sub-band closely over hours or days: the one you plan to use, or one that looked busy in a
survey. It gives the fullest picture of that sub-band through the day, busy and quiet times alike, but
nothing about the others.
The scanner visits the sub-bands in your list one after another, listening to each for the set number of
seconds, round after round.
Choose it to compare sub-bands and find the quietest one for a new network. Each sub-band is heard only part
of the time (one eighth with all eight in the list), so let it run for several hours, ideally a whole day, to
cover busy and quiet times.
In Survey mode, the scanner listens to each sub-band for the number of seconds entered, then moves to the next
channel in the list. It takes about 20 seconds to switch FSBs. No data is collected during an FSB change. The
scanner cycles through the list until the scan's duration is over or you press Stop Scan.
The default is 360 seconds (6 minutes) per FSB so a full round of all 8 takes about 50 minutes. Lower values
sample each sub-band more often but lose more time to switching. Below 300, each visit is too short to judge on
its own. 900 seconds (15 minutes) is the maximum. To scan a band for longer than 15 minutes, use the Dwell
mode.
When the time is up, the scan stops by itself and the results stay on the gateway. Stop Scan,
at the top of the page, ends it sooner.
5. Start the scan
Would you like to start a LoRaWAN Traffic Scan now?
All set
Scan settings
What would you like to record?
Record a LoRaWAN traffic scan
Consolidated scan and report
A consolidated scan measures each sub-band (FSB) in two ways, one straight after the other, and combines them
into one report that rates how available each FSB is for new LoRaWAN sensors.
How it works
For each FSB you choose, in turn:
Spectral scan. LoRa is switched off and the gateway's spectral-scan radio measures all the radio
energy on the FSB's eight channels: anything transmitting there, LoRaWAN or not.
LoRaWAN traffic scan. LoRa is switched back on, on that FSB, and the gateway records the LoRaWAN
traffic it hears for the same length of time.
Then it moves on to the next FSB. At the end the gateway's own LoRa settings are put back.
What the report tells you
LoRaWAN traffic: how busy each FSB is with other LoRaWAN networks, so how often a new sensor's
uplink would collide with theirs.
Other signals: the spectral scan's busy time minus the LoRaWAN traffic it also saw: transmitters
that aren't LoRaWAN (RFID readers, meters, alarm and remote-control links). They don't back off, and an
uplink that overlaps one is usually lost.
Noise floor: how far each FSB's background noise sits above the quietest channels. A raised floor
shortens every sensor's range.
The verdict: the chance a new sensor's uplink gets through, graded from Quiet to Busy, and the
best FSB to use.
How long it takes
Each scan runs 10 to 60 minutes per FSB (15 by default), so each FSB takes twice that, plus about a minute to
switch. A 30-second test run is offered too, to check that every step works; its results are not valid. All 8 FSBs at 15 minutes take about 4 hours 10 minutes. 10 minutes is the shortest that gives
dependable figures: many sensors report only every 10 to 15 minutes, and a shorter LoRaWAN scan would miss
them.
Each FSB is measured at a different time, so traffic that comes and goes during the day can favour one FSB
over another. For an important site, run it again at another time of day.
While it runs
The gateway receives no LoRaWAN traffic during the spectral scans, so don't use it for anything else. Stop Scan
ends the consolidated scan early; the FSBs finished by then are kept for the report.
Consolidated scan settings
For testing only. 30 seconds is too short to catch most LoRaWAN
devices or occasional signals, so the results will not be valid. The report is marked as a test.
Ready to scan
See the data live?
Would you like to see the charts and graphs fill in as the data is collected? Choose No to see only a progress
bar while the scan runs; the results are recorded either way, and you can switch to the live charts at any time.
Configure scanning
Live scan: the data is displayed while it runs but not recorded:
it isn't kept, and it doesn't appear in reports or saved scans. It runs until you press Stop Scan.
For testing only. 30 seconds is too short to catch occasional
signals, so the figures will not be valid. The results are marked as a test.
Type of LoRaWAN scan
The scanner listens on whatever sub-band the gateway is already set to and never changes the radio.
Choose it when the gateway must stay on its sub-band, for example one that goes back into service right
after, or when you only need to know about the sub-band your own network uses. It is the least disruptive
choice, but it tells you about one sub-band only.
The scanner sets the radio to the sub-band you choose and stays there, hearing all of its traffic.
Choose it to watch one sub-band closely over hours or days: the one you plan to use, or one that looked busy
in a survey. It gives the fullest picture of that sub-band through the day, busy and quiet times alike, but
nothing about the others.
The scanner visits the sub-bands in your list one after another, listening to each for the set number of
seconds, round after round.
Choose it to compare sub-bands and find the quietest one for a new network. Each sub-band is heard only part
of the time (one eighth with all eight in the list), so let it run for several hours, ideally a whole day,
to cover busy and quiet times.
In Survey mode, the scanner listens to each sub-band for the number of seconds entered, then moves to the
next channel in the list. It takes about 20 seconds to switch FSBs. No data is collected during an FSB
change. The scanner cycles through the list until the scan's duration is over or you press Stop Scan.
The default is 360 seconds (6 minutes) per FSB so a full round of all 8 takes about 50 minutes. Lower
values sample each sub-band more often but lose more time to switching. Below 300, each visit is too short
to judge on its own. 900 seconds (15 minutes) is the maximum. To scan a band for longer than 15 minutes,
use the Dwell mode.
Gateway Readiness Check
Checking the gateway's LoRaWAN settings…
Step by step: sign in, backup, settings, scan.
Commissioned this gateway with the Site Survey Tool app on a tablet? It sets all of
this up automatically when you start a traffic scan, so there is nothing to change here.
This gateway is serving a LoRaWAN network
While it is set up for scanning, those devices can't reach their network. Put the settings back after
the scan (see User defined settings below).
1. Save a backup first
In mPower choose Administration › Save/Restore and save the configuration to your computer. This is
strongly recommended before changing any LoRaWAN setting.
2. The settings the scanner needs
Setting
Now
Needed
—
Change them in mPower under LoRaWAN › Network Settings: Mode Packet
Forwarder; in the packet forwarder's network settings, Server Address 127.0.0.1, Upstream Port
1700 and Downstream Port 1700. Then Save and Apply. This page updates by itself.
Firewall: the app opens TCP 8080 itself on the gateway's LAN interfaces (the LAN bridge and any LAN
port outside it) and re-opens it within a minute after any Save and Apply, so no rule is needed in mPower for a
computer on the LAN. If the
gateway reaches your network through its WAN port (common on installed gateways), add a rule in mPower under
Firewall › Input Filter Rules that accepts TCP 8080 on WAN, ideally only from your computer's address, and
remove it after the scan.
Or let the app change them: it sets the mode, server address and ports in mPower, saves
them and restarts LoRa (about 10 seconds, no reboot). Nothing else is changed.
3. What switching modes keeps
Switching from Network Server or Basic Station mode to Packet Forwarder keeps that mode's settings (devices,
whitelist, keys, the Basic Station server). Only the packet forwarder's server address and ports change for the
scan, so note them and put them back afterwards.
User defined settings (to restore after the scan)
—
Choose a Task
Record a LoRaWAN traffic scan or a spectral scan. The results are saved for reports.
Watch LoRaWAN traffic or the spectrum as it happens, without recording it.
Make reports from saved scans, or export the scan data as a CSV file.
Step through backing up and setting up the gateway, then starting a scan.
Scanning
Consolidated scan
Other signals · share of samples at least 8 dB above each channel's own noise floor
Noise floor · dB above the quietest channel measured so far
902.3 MHz → 914.9 MHz, the 64 uplink channels of FSB 1–8 · the FSB being scanned now is in
colour, FSBs scanned earlier in light grey, FSBs not scanned yet are flat · updated every few seconds · hover over
(or tap) a bar for its details · LoRaWAN packets count as signals here too: the report separates them out
Live analysis
· the sub-bands heard in this scan
Waiting for the scan's first figures…
· last 60 s utilization per channel
902.3 MHz → 914.9 MHz (125 kHz ch 0–63) · 500 kHz ch 64–71 at right · the FSB being scanned now is in colour, FSBs scanned earlier in light grey · waterfall: newest at top, scroll down for earlier FSBs, colour = RSSI · hover over (or tap) a bar for its details