InnerWeb
Skip to main content

Unique transmitter identifiers: implementation notes

When mounting hundreds of transmitters, the most common error is a repeated identifier or a transmitter assigned to the wrong location. Both mistakes are invisible at the mounting stage and surface only as position jumps on employees' routes.

19,900
pairs to compare for 200 transmitters
Source: sample calculation
11,000
transmitters in the city project
Source: project card

Note 1: why a duplicate breaks the position

Two physical transmitters with the same identifier placed hundreds of metres apart produce a single position in the system. The system sees one identifier and does not know that the signal comes from two places, so the averaging of the position pulls the result between them.

The position results from the signals of several transmitters averaged on the map. A single faulty transmitter among many usually does not break the position completely, but it lowers accuracy in its surroundings. That is why an error can remain unnoticed for weeks.

Note 2: wrong assignment of location

The second type of error is a transmitter placed on a road but assigned in the data to a warehouse. Radio beacons located on a road but assigned to a warehouse draw a route jump. On employees' routes this shows up as a sudden jump and return.

The good news is that a wrong position in the data is corrected once for all future routes. The bad news: routes already saved with a jump must be assessed taking this error into account. That is why correction during mounting is cheaper than fixing it after months.

Transmitter pairs to compare manually

Transmitter pairs to compare manuallyHorizontal bar chart: 19,900 pairs for 200 transmitters, 179,700 for 600 and 499,500 for 1,000.0100,000200,000300,000400,000500,000pairs200 transmitters200 transmitters: 19,900 pairs19,900600 transmitters600 transmitters: 179,700 pairs179,7001,000 transmitters1,000 transmitters: 499,500 pairs499,500
Source: Sample calculation: n(n-1)/2 for the given number of transmitters.

Note 3: control of the manufacturer's identifiers

The application accepts only transmitters with a manufacturer identifier, and a foreign transmitter is rejected. This protects against accidentally adding equipment from outside the network, but it does not protect against a duplicate among the network's own transmitters, so uniqueness must be checked separately.

Keep a register: identifier, location, date of mounting, person, photo. After each day of mounting, export the list and check in a spreadsheet that no identifier appears twice. With several hundred units, checking by sorting and counting takes a few minutes.

Note 4: scale and sample calculation

Manually comparing each transmitter with every other makes no sense: for 200 units this is 19,900 pairs, for 600 units 179,700 pairs, and for the city project with 11,000 transmitters over 60 million pairs. The number of pairs is n times (n minus 1), divided by 2, and it grows with the square of the count.

That is why the uniqueness check is performed automatically: sorting the list of identifiers and counting repetitions grows linearly with the number of units. At the scale of 11,000 transmitters in 95 facilities, such a check is a requirement, not an extra to mounting.

Note 5: order of steps during mounting and acceptance

Before mounting, prepare the plan with the places and the list of identifiers for each zone. During mounting, scan or enter the identifier at each transmitter and confirm the location at once. After the working day, check for duplicates and missing positions.

Coverage with transmitters is calibrated at the start of the deployment, before alarms are launched. Before this step the identifier register must be clean, because calibration on wrong data sets the power on wrong assumptions.

Note 6: acceptance and keeping the register up to date

Network acceptance ends with a test walk with a phone along all routes, comparing positions with the plan. A discrepancy usually points to a duplicate or a wrong assignment, so these two causes are checked first.

During maintenance the register is updated after each replacement or addition of a transmitter. When a battery is replaced the identifier stays the same, and a change of place requires a change of location in the data. The administrator then has one source of truth for the network.

Example calculation

Pairs of transmitters to compare

Assumptions
ParameterValue
Number of transmitters n200 units
Formulan(n-1)/2 pairs

Result: 19,900 pairs for 200, 179,700 for 600

Note: Sample calculation; illustrates why the uniqueness check must be automatic.

Video

Frequently asked questions

What happens when two transmitters have the same identifier?

The system shows one position for both if they stand far apart. The position is inaccurate in their surroundings, and the error often remains unnoticed.

Will the application reject a foreign transmitter?

Yes, the application accepts only transmitters with a manufacturer identifier. It does not, however, protect against a duplicate identifier among your own transmitters.

How is a transmitter assigned to the wrong location corrected?

The position is corrected once in the data, and the change works for all future routes. Routes already saved with a jump are assessed taking the error into account.

Let us tidy up the transmitter register

We will help prepare the identifier register and the uniqueness check procedure before mounting.

Let's talk