InnerWeb
Skip to main content

Duplicate transmitter ID and route jumps: diagnosis

On the map, a vehicle route swings off the road and returns, although the transmitter looks correctly described. The most common cause is a duplicated identifier: two physical transmitters with the same major and minor pair in distant places. Below is the sequence of steps for the technician.

Symptom: the route swings out of the road corridor

The technician receives a report: on the online map, the delivery route makes a sharp sideways jump at one point, outside the road corridor, and returns to the correct line at the next point. It repeats on subsequent runs of the same vehicle, so it is not a one-off disturbance.

The delivery route on the map is not a GPS track. It is a line connecting the positions of transmitters detected by the phone or the tracker. If the system concludes that the vehicle heard a transmitter at a given place, it draws the point exactly there. That is why a jump usually means that some transmitter is recorded at a different place than where it hangs.

Why the transmitter looks correct

Each beacon has an identifier made of a major and minor pair, and the system assigns this identifier to one place on the map. In the admin panel the entry therefore looks correct: there is an identifier, there are coordinates, there is a description. The error is not visible, because it does not lie in a single entry, but in the relation between the entry and reality.

For the system, two physical transmitters with the same identifier hung in distant places are indistinguishable. The phone hears the signal from one or the other and always receives the same position from the database. Changing the recorded position does not solve the problem, it only moves it to the other place.

Route jump diagnosis steps: time per step, sample calculation

Route jump diagnosis steps: time per step, sample calculationBefore and after chart: the time spent searching for the error shortens after applying the comparison with the previous route point.020406080100minWithout comparison with neighbouring points (Searching for the error): 90 min90 minWith comparison with the previous point (Searching for the error): 25 min25 minSearching for the errorWithout comparison with neighbouring points (Correction): 20 min20 minWith comparison with the previous point (Correction): 20 min20 minCorrection
  • Without comparison with neighbouring points
  • With comparison with the previous point
Source: Sample calculation: assumed working times of the technician, not a measurement from a deployment

Step-by-step diagnostic procedure

An effective diagnosis of a jump is a comparison of the route point with the previous and next points of the same tracker. The previous point shows where the vehicle really was, so it is its neighbourhood that must be checked in the field, not the place where the route swings out.

Step 1: identify the jump point

From the list of route points, read the transmitter that generated the displaced point and its major and minor identifier. Record the time and the tracker identifier so that the situation can be reconstructed.

Step 2: check where the vehicle really was

Compare the displaced point with the previous and next points of the same tracker. If the vehicle was moving along the road and the displaced point lies to the side, then the recorded position of the transmitter does not match the place where the vehicle heard it.

Step 3: look for a second transmitter with the same identifier

Check in the register whether the same major and minor pair appears twice on the list, and in the field, or near the previous point, whether a transmitter with an identifier identical to the one from the jump is hanging. Only finding the duplicate closes the diagnosis.

Step 4: assign a unique identifier and correct the record

Change the identifier of one of the transmitters to a unique one, and record its actual position in the system. Make the change in the admin application so that it reaches the audit log. Changes made outside the application bypass the log, so afterwards it is impossible to establish who made them and when.

What happens to routes already recorded

Recorded route points are immutable snapshots taken at the time of reading. After correcting a transmitter's position we do not rewrite the history of deliveries already registered; we improve the result for future runs. Old jumps remain in the history and it is worth marking them in the service note, so that the analyst knows they come from the period before the correction.

This behaviour is intentional: the history is meant to reproduce what the system saw at a given moment, not what we know today about the error. As a result, audit evidence does not change after the fact.

How to limit repetitions

Duplicate identifiers usually arise during installation: a technician takes transmitters from several batches and hangs them in different halls, entering the identifier from the installation card. A simple preventive measure is a register in which each major and minor pair may occur only once, and a check in the application before closing the installation order.

The second measure is a periodic review of routes for jumps. If one tracker repeatedly produces displaced points in the same place, this is a sign that something is recorded at that place inconsistently with the actual state.

Video

Frequently asked questions

Is a route jump a transmitter failure?

Usually not. The transmitter works, but its recorded position or identifier does not match reality. Replacing the battery or the transmitter will not remove such a jump.

Is it enough to correct the coordinates in the system?

If the cause is a duplicated identifier, changing the coordinates moves the problem to the other place where the second copy hangs. One of the transmitters must be given a unique identifier.

Will the correction change the existing routes?

No. Recorded points are immutable snapshots taken at the time of reading, so the correction affects future runs and the history stays unchanged.

Where can you see who changed a transmitter?

Edits made in the admin application go to the audit log. Changes made outside the application bypass it, so they are not visible.

Order in transmitter identifiers

We will review the transmitter register and the routes for jumps together with you. Book a conversation with the InnerWeb team.

Let's talk