Starting point: a large site and a short deadline
The scenario covers a production plant with halls, internal roads and a large outdoor storage yard. Wi-Fi works in the offices and in part of the halls, but the yard, loading ramps and outer roads stay without a network, and GSM coverage there is uneven. The maintenance manager has a task: within 3 weeks, check whether a worker alone on the yard can raise an alarm and be visible on the map.
This is a deployment scenario, not a description of a finished installation. We show how such a pilot can be set up around system behaviour known from the feature documentation: a LoRa watch, a gateway that translates radio frames into HTTP requests, and a panel with a map. The figures come from the radio parameters and from a sample calculation with stated assumptions.
How the LoRa watch reaches the system
The LoRa watch works without Wi-Fi. At a set interval it wakes from deep sleep, scans for BLE beacons for about 3 s and sends one frame with the visible beacons, the battery level and the status. The default pulse period is 120 s. The gateway receives the frame and translates it into the existing HTTP request to the system, so nothing changes on the application side.
The radio works in the 869.525 MHz band, inside the 869.4 to 869.65 MHz sub-band, with a 500 mW ERP limit and a 10% duty cycle. The parameters are +14 dBm power, SF9 and a 125 kHz channel width. A frame lasts about 230 ms on air, so at a 120 s period the watch occupies the channel for about 0.2% of the time, far below the limit.
- The gateway confirms receipt of the frame in about 250 ms, before the HTTP request, and adds the link RSSI and SNR to the confirmation.
- Frames are encrypted with AES-128-CCM, with an 8-byte authentication code and replay counters.
- The watch's time comes from the gateway, which synchronises via SNTP.
Channel load from 100 watches by pulse period
A three-week pilot plan
Three weeks are enough when the scope is narrow. We propose three stages, and each one ends with a measurable result rather than a general impression.
Week 1: gateway and map
Install one gateway where there is power and a link, ideally on a building visible from the yard. Place BLE beacons on the internal roads about every 100 m and in the chosen hall, one beacon per 100 to 200 m2. Run a coverage test by walking the site with the watch, and read RSSI and SNR from the gateway confirmations.
Week 2: watches and SOS
A few watches for operators and lone workers. Run the SOS test from the points furthest from the gateway, together with the dispatcher in the panel. Record the time from pressing the button to the alarm appearing.
Week 3: results and decision
A summary of coverage, SOS delivery time and battery consumption. A decision on whether the site needs a second gateway, a repeater or an LTE module, and whether the scale justifies a talk about LoRaWAN.
What happens outside beacon range
On a large yard the watch does not always hear a beacon. When it hears none, the frame is still sent and the system uses the last known location. Battery level, status and inactivity detection therefore reach the dispatcher even in places without BLE coverage.
On SOS, after the HTTP request, the gateway sends a second frame with the result. The watch then shows that the alarm reached the system. The worker on the yard does not have to guess whether the button worked, and does not have to press it a fifth time.
An important limitation: the last known position is an approximation, not a measured location. The dispatcher sees this in the panel and should treat such a point as a search area.
Sample calculation: how many watches per channel
The 10% duty-cycle limit applies to a single device, but all the watches within gateway range share the channel. Take a 230 ms frame. At a 120 s period one watch loads the channel by 0.19%, so 100 watches give about 19% channel load. At a 300 s period the same group gives about 7.7%.
In a random-access model, where watches transmit without coordination, the share of collision-free frames is roughly e raised to the power of minus twice the load: about 68% at 19% load and about 86% at 7.7%. This is a simplified model for choosing the period in advance, not a guarantee. The period is set centrally in the panel within 30 to 3600 s and returns to the watch in the system response, so the pilot result can be applied at once.
Channel load from a group of watches
| Parameter | Value |
|---|---|
| Frame airtime | 230 ms |
| Watches per gateway | 100 pcs |
| Pulse period | 120 s |
Result: Approx. 19% channel load at 120 s and approx. 7.7% at 300 s
Note: Sample calculation on a simplified random-access model; the pilot measures the real share of received frames.
Video
Frequently asked questions
Does the LoRa pilot need Wi-Fi across the whole site?
No. Wi-Fi or another link is needed only at the gateway, which passes data to the system. The watches communicate with the gateway by radio.
What if the watch is out of BLE beacon range?
The frame is still sent and the system uses the last known location. Status, battery and inactivity reach the dispatcher.
How does the watch know that the SOS arrived?
After the HTTP request the gateway sends a second frame with the result, and the watch shows that result to the user.
Let's plan a pilot on your site
We will present a 3-week LoRa pilot plan for the yard and the halls, with measurable success criteria. We invite you to a demo conversation.
Let's talk