InnerWeb
Skip to main content

How to plan LoRa frequencies at a plant

Channel collisions rarely come from faulty hardware. They usually come from the lack of a plan: two networks land on the same channel because neither knew about the other. This guide shows how to record the radio parameters, find overlapping channels and keep evidence of the decision for an audit.

869.4-869.65 MHz
sub-band with the 10% airtime limit and 500 mW ERP power
Source: karta
+14 dBm
transmission power of the watch
Source: karta

Why a plan is needed

Several radio systems in the 868 MHz band often work at one plant: watches with gateways, sensors, meters and sometimes a mesh network. Each has its own settings, and the IT or maintenance department rarely sees all of them at once.

A frequency plan is a document that gathers these settings in one place and shows where two systems compete for the same channel. Without it the problem appears as lost frames that cannot be linked to any fault.

Radio parameters to record

The radio of the watch and the gateway works in the 869.525 MHz channel, within the 869.4-869.65 MHz sub-band, where the power limit is 500 mW ERP and the airtime limit is 10%. The modulation parameters are +14 dBm power, SF9, a 125 kHz bandwidth and a private sync word.

The private sync word means the gateway receives only its own frames, not every LoRa frame nearby. It is not, however, protection against occupying the channel: a foreign transmitter on the same frequency still uses airtime and can jam reception.

  • Centre frequency and the sub-band in which the airtime limit applies.
  • Spreading factor (SF), channel width and transmission power.
  • Sync word and the way frames are encrypted.
  • Number of transmitters, beacon interval and the expected channel occupancy.
  • Locations of gateways and repeater gateways, and the hop counter.

Shared channel occupancy: watches and mesh on one channel versus separated

Shared channel occupancy: watches and mesh on one channel versus separatedBefore and after chart: on one channel the total occupancy is 38%, after separating the channels each system takes 19%010203040%One channel (Watches): 19 %19 %Separated channels (Watches): 19 %19 %WatchesOne channel (Mesh): 19 %19 %Separated channels (Mesh): 19 %19 %MeshOne channel (Total on the channel): 38 %38 %Separated channels (Total on the channel): 19 %19 %Total on the channel
  • One channel
  • Separated channels
Source: Example calculation: 100 watches every 120 s, 230 ms frame; mesh load assumed to be the same

Mesh network: where the plan most often fails

The variant of backhaul with a mesh network as the collective link requires a second radio at the gateway, an MQTT broker, a consumer on the system side and a separate frequency plan. The reason is specific: the default mesh slot overlaps the 869.4-869.65 MHz channel in which the watches and gateways work.

If both systems stayed on the same channel, the watch frames and the mesh frames would occupy the same airtime. The solution is to move the mesh network to another channel, or to choose the simpler variant: a repeater gateway that relays InnerWeb protocol frames with a hop counter of 2-3 and deduplication.

One radio, two protocols: a hardware limit

Two different radio protocols on one SX1262 chip cannot be listened to at the same time. A dual-radio gateway therefore means two boards or two radio modules, and the frequency plan must assume that each radio has its own channel.

How to build the plan step by step

First make an inventory: a list of all radio systems in the 868 MHz band, together with the channel, the power and the locations of the antennas. Then mark the channels on the frequency axis and check whether they overlap. Finally calculate the channel occupancy for each system and record the margin.

Example calculation: a watch frame lasts about 230 ms, and 100 watches sending every 120 s occupy the channel for about 19% of the time. If a mesh network with a similar load shared the same channel, the combined occupancy would approach 40%, which with random channel access means a clear rise in collisions.

Evidence of the decision and maintaining the plan

The plan document should contain the channel table, photos or plans of the gateway locations, the result of the coverage test and a record of who approved the change. This is audit evidence that the radio parameters were chosen deliberately.

The plan must be updated with every change: a new gateway, an increase in the number of watches or the introduction of another radio system. It is worth appointing one person responsible for the channel register.

Video

Frequently asked questions

Does the private sync word protect against collisions?

No. It makes the gateway receive only its own frames, but a foreign transmitter on the same frequency still uses airtime and can jam reception.

Can one gateway listen to two protocols?

On one SX1262 chip two different protocols cannot be listened to at the same time. A dual-radio gateway means two boards or two radio modules.

When is a separate frequency plan needed?

Always when another system in the 868 MHz band works next to the watches and gateways, in particular a mesh network whose default slot overlaps the watch channel.

A frequency plan for your site

We will help you record the radio parameters and find overlapping channels before the first pilot. Let us arrange a technical call.

Let's talk