Why the test is needed
A change to beacon data looks finished in the panel as soon as it is saved. That does not prove nothing is happening in the field: phones still receive signals from devices physically hanging in the hall. Only the record of route points shows whether the system has stopped placing vehicles at the wrong identifier.
There is also an organisational reason. Disabling a duplicated identifier switches off both twin devices, including working ones, so that navigation point is lost until a field visit. The administrator should have proof that the effect is the one planned, and not a bigger one.
How disabling works and what may be changed
Disabling a duplicated identifier from positioning means changing its major number to a value that no device broadcasts. The position, minor and location stay, so restoring it is a one-number change.
Spare entries of inactive beacons are not deleted, because a device may start broadcasting again. Deleting the entry would take away the system's ability to recognise that device if it returned to work after a battery change or restart.
Route points in 10 minutes: before and after disabling (example)
- Before the change
- After the change
Test procedure in a few minutes
The test consists of a measurement before the change, the change itself and a measurement after it. The whole cycle fits into 15 to 20 minutes, provided there is at least one vehicle or person with an active locator in the warehouse.
- Record the time and the number of route points of all beacons for the last 10 minutes as the state before the change.
- Change the major number of the disabled identifier to an unused value.
- Wait a few minutes, ideally as long as a full pass of a vehicle through the zone takes.
- Count the route points recorded since the change for the disabled identifier: there should be zero.
- Count the points for neighbouring beacons: they should keep increasing, because if they stopped, the problem is the whole zone, not a single identifier.
- Record the result with the time in the change log.
How to read the result
Zero points for the disabled identifier and a continued increase for the neighbours means the change worked. If the disabled identifier still adds points, there is a second entry with the same values, or the wrong entry was disabled, the one that actually transmits.
If the increase stopped across the whole zone, check whether the change affected too many devices. Remember that route points are immutable records of the signal moment: the correction applies only to future deliveries, and old routes keep the jump.
Documenting the change
In the change log, record the identifier, the previous major number, the new number, the time of the change, the number of points before and after, and the person who made the change. Such an entry lets you answer after a month why a navigation point disappeared and plan a field visit.
Checklist
Video
Frequently asked questions
How long should I wait for the test result?
A few minutes, as long as it takes a vehicle or a person with a locator to pass through the zone. The whole test fits into 15-20 minutes.
What if the disabled beacon still adds points?
Check whether a second entry with the same major and minor values exists, or whether you changed an entry other than the one that actually transmits.
Why not delete the inactive entry?
Because the device may start broadcasting again, for example after a battery change. The entry lets the system recognise it.
Let's run the test together
We will show how to count route points after a beacon change in your warehouse and how to record the result in the log.
Let's talk