The Diagnostics screen on the Handheld POS terminal provides important technical details about the device and its connection. This information is useful for troubleshooting issues with support by showing specific application, hardware, and network latency information all in one place.

• Device & App Details: Displays key information such as the installed POS Application Version, connected Environment and Base URL, device Battery Level, and specific hardware details like the Device Model, Serial Number, and Firmware Version.
• Network Latency Test: Includes a tool to measure the connection quality to the Salido backend, showing the Average round-trip time (RTT) and the individual Deltas for each test ping in milliseconds.

To Run a Latency Test and View Diagnostics on the Handheld POS:

1. Locate the handheld POS device you'll be using, enter your PIN, and tap OK

2. Tap the three lines at the top left of the screen

3. Tap Diagnostics

4. View Diagnostics

5. Run the Latency Test by tapping the refresh button

What the results tell us:

• Deltas (ms): This shows the individual round-trip time (RTT) in milliseconds for each separate request sent to the Salido backend API during the test. The list displays the time taken for each ping to travel from the terminal to the backend and back again.
• Average (ms): This is the calculated average round-trip time in milliseconds, based on the successful requests made after the initial connection setup. It provides a representative measure of the ongoing connection latency.
• Errors: This field counts the number of requests that failed to complete successfully during the test (e.g., timed out or received an error response from the server). A value of "0" indicates all test requests were successful.

Why the First Delta is Larger:

The first delta value listed is typically higher than the subsequent ones because it includes the additional time required for the initial TCP connection setup and HTTP handshake with the backend server. This value is deliberately excluded from the average as not to skew the results. Once this connection is established, the browser keeps it open for subsequent requests in the test sequence. These later requests don't have that initial setup overhead, so their delta times represent a more direct measure of the network's round-trip latency over the active connection.

Interpreting the Results

The most important value to check is the Average (ms). This number indicates the typical round-trip communication time between the POS terminal and the Salido backend. Use the following benchmarks to evaluate your connection quality:

• Ideal: An average latency of 100 ms or lower indicates a strong, responsive connection.
• Acceptable: Averages between 100 ms and 150 ms are generally acceptable, though lower is always better.
• Potential Issues: Averages around 500 ms may lead to noticeable delays in POS operations.
• Problematic: Averages consistently above 750 ms are likely unusable and will significantly impact performance.

Action Required:

If the Average (ms) shown by the test is consistently significantly above 150 ms, please contact Salido Support for assistance in diagnosing potential network issues.