Network Latency Requirements for RTLS Solution

In a high-performance Real-Time Location System (RTLS), network latency is a critical factor that directly impacts system efficiency and accuracy. While latency itself is important, the key to seamless RTLS operation lies in stability and consistency. For RTLS to perform optimally, network latency needs to stay below 20ms and remain consistent across anchors and clients

With latency over 20ms, your RTLS system may start to experience delays, which can compromise the accuracy of location updates and overall system reliability. This threshold is crucial for maintaining the responsive and real-time nature of your RTLS solution.

Latency Testing Using Tracert

To measure the network latency between the RTLS server (or any device in the data center) and anchors or other clients on-site, the tracert (trace route) tool can be used. This tool helps identify network delays by showing the path data packets take and the time it takes to reach each hop.

Steps to Perform a Latency Test with Tracert:

1) Open Command Prompt/Terminal

Windows: Press Win + R, type cmd, and press Enter.
Linux/macOS: Open Terminal.

2) Run the Tracert Command:

In Windows

tracert [destination IP or domain name]

In Linux/macOS

traceroute [destination IP or domain name]

Replace [destination IP or domain name] with the IP address of the RTLS server, anchor, or any client device. For example:

tracert 192.168.1.1

3) Analyze the Tracert Output

The tracert tool will show the route taken by the packets and the time (in milliseconds) it took for each hop. A typical output might look like this:

Tracing route to 192.168.1.1 over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  router.local [192.168.0.1]
  2    5 ms     6 ms     5 ms  10.10.10.1
  3    10 ms    9 ms     8 ms  192.168.1.1

Focus on the final hop (the RTLS server or anchor). This latency value reflects the time it takes for packets to reach the destination. Ideally, this latency should be below 20ms and stable across tests.

4) Evaluate Latency Consistency

Pay attention to latency fluctuations between hops and within the same hop over multiple tests. If you notice spikes or a latency consistently above 20ms, this could indicate network instability.
Inconsistent latency—for example, large variances between consecutive hops—can degrade RTLS performance, even if the overall latency is within acceptable limits.

5) Interpret Results

If latency consistently stays under 20ms and shows little fluctuation, the network is performing well for RTLS operations.
Any latency that exceeds 20ms or shows significant variation should be investigated further, as it could affect the accuracy and performance of the RTLS system.