InnerWeb
Skip to main content

Implementation notes: location outside transmitter range

The worker goes down to the cable basement or behind a tank, where transmitters no longer hear him, but the watch still sends pulses to the server. What will the dispatcher see then? Below are implementation notes for the system administrator: how the last known location works and how to configure a site so that as few such places as possible are left.

100 m
spacing of transmitters on plant roads
Source: company facts
100-200 m2
area per transmitter inside a building
Source: company facts
< 2 min
from detecting no movement to notifying the response team
Source: process description (card)

How the system behaves outside transmitter range

The device worn by the worker periodically sends a pulse: which transmitters it hears, with what signal strength, battery level and status. From these data the platform determines the position in real time. When no transmitter is audible, the LoRa watch still sends a frame and the node forwards it. The backend then substitutes the last known location.

As a result, battery, status and no-movement reach the platform even outside transmitter range. The dispatcher does not lose the worker from view: he sees the place where the worker was last heard, and the fact that the signal is still arriving.

What this means for the dispatcher

The last known location is not the current position, but a point from which the search should begin. If the worker disappeared from the map near the entrance to the underground part of the site, the dispatcher knows where to send help. The pulse with battery and status confirms that the device is alive, so the lack of a position does not mean a watch failure.

It is worth training dispatchers that the difference between no transmitters in range and no pulse is fundamental. The first state is a coverage gap. The second may mean a device problem or a radio range problem.

Transmitter placement rules

Transmitter placement rulesBar chart: 100 metre spacing on roads, and 100 and 200 square metres per transmitter inside a building.050100150200m or m2 per transmitter (as labelled)Road: spacing in metres: 100 m or m2 per transmitter (as labelled)100Road: spacing in metresBuilding: lower bound in m2: 100 m or m2 per transmitter (as labelled)100Building: lower bound in m2Building: upper bound in m2: 200 m or m2 per transmitter (as labelled)200Building: upper bound in m2
Source: InnerWeb company facts: plant roads roughly every 100 m, and inside a building one transmitter per 100-200 m2

Stage 1: coverage audit before go-live

Before a site is launched, the administrator walks the whole area with a watch and marks the places where transmitters are not heard. The starting rule is plant roads roughly every 100 m and one transmitter per 100-200 m2 inside a building. The position is calculated from signals of many transmitters averaged on the map, without GPS, so a coverage gap usually results from shielding, not from a lack of satellites.

Resolve each gap with a decision: add a transmitter, accept the gap and describe it on the map, or change the working procedure in that spot.

Stage 2: decide where to leave a gap

Not every place needs a transmitter. A process pipe visited once a year does not deserve separate infrastructure if the last known location points to the right entrance. A place visited daily by a person working alone does require full coverage. Describe the decision next to the checkpoint on the map, so that the next administrator does not rebuild it from scratch.

Stage 3: alarm settings for zones without coverage

The no-movement alarm infers lack of movement from the pulses. In a working production deployment it warns after 20 s without movement, and after a further 30 s without a response it raises an alarm. The time from detection to notifying the response team is under 2 minutes. Because frames also arrive outside transmitter range, this mechanism works in zones without coverage too, only with less precise location information. Check this in a test before you trust the configuration.

Pitfalls to watch for

The most common implementation errors come from assumptions, not from the technology.

  • Treating the last known location as the worker's current position.
  • No alarm test in a zone without coverage before the site goes live.
  • Too few transmitters in a building, so that averaging from many sources loses its sense.
  • No description of gaps on the map, so the dispatcher does not know that the place is known to lack transmitter coverage.
  • Confusing lack of transmitters in range with lack of pulse.

Video

Frequently asked questions

Do SOS and no-movement still reach the server outside transmitter range?

Yes. The gateway sends a frame even when it hears no transmitter, so status and no-movement reach the platform together with the last known location.

Is the last known location the worker's current position?

No. It is the place where the worker was last heard. It serves as the starting point of a search.

How can the number of places without coverage be limited?

Through an audit with a watch before go-live and placement by the rule: roads roughly every 100 m, and one transmitter per 100-200 m2 in a building.

Let us check coverage on your site

We will walk your site with a watch, mark the coverage gaps and decide where to add transmitters and where to leave a gap.

Let's talk